| Message ID | 20180516083414.6407-1-judge.packham@gmail.com |
|---|---|
| State | Accepted |
| Delegated to: | Tom Rini |
| Headers | show |
| Series | [U-Boot] Remove CONFIG_MVGBE from config_whitelist.txt | expand |
On 16 May 2018 at 02:34, Chris Packham <judge.packham@gmail.com> wrote: > Now that there are more boards defining this it can be removed from the > whitelist. > > Signed-off-by: Chris Packham <judge.packham@gmail.com> > --- > > scripts/config_whitelist.txt | 1 - > 1 file changed, 1 deletion(-) Reviewed-by: Simon Glass <sjg@chromium.org>
On Wed, May 16, 2018 at 08:34:14PM +1200, Chris Packham wrote: > Now that there are more boards defining this it can be removed from the > whitelist. > > Signed-off-by: Chris Packham <judge.packham@gmail.com> > Reviewed-by: Simon Glass <sjg@chromium.org> Applied to u-boot/master, thanks!
Hi Tom, On Tue, May 29, 2018 at 7:12 AM Tom Rini <trini@konsulko.com> wrote: > On Wed, May 16, 2018 at 08:34:14PM +1200, Chris Packham wrote: > > Now that there are more boards defining this it can be removed from the > > whitelist. > > > > Signed-off-by: Chris Packham <judge.packham@gmail.com> > > Reviewed-by: Simon Glass <sjg@chromium.org> > Applied to u-boot/master, thanks! Not a big deal but it appears you picked up v1 when there was a v2 posted http://patchwork.ozlabs.org/patch/921018/ the only change was fixing a typo in the commit message so no harm done. Just wondering if there is something I should be doing to make this more obvious? Specifically does patman need to grow support for dealing with In-reply-to:?
On Tue, May 29, 2018 at 11:12:22AM +1200, Chris Packham wrote: > Hi Tom, > On Tue, May 29, 2018 at 7:12 AM Tom Rini <trini@konsulko.com> wrote: > > > On Wed, May 16, 2018 at 08:34:14PM +1200, Chris Packham wrote: > > > > Now that there are more boards defining this it can be removed from the > > > whitelist. > > > > > > Signed-off-by: Chris Packham <judge.packham@gmail.com> > > > Reviewed-by: Simon Glass <sjg@chromium.org> > > > Applied to u-boot/master, thanks! > > Not a big deal but it appears you picked up v1 when there was a v2 posted > http://patchwork.ozlabs.org/patch/921018/ the only change was fixing a typo > in the commit message so no harm done. Just wondering if there is something > I should be doing to make this more obvious? Specifically does patman need > to grow support for dealing with In-reply-to:? Unfortunate timing. I grabbed v1 on Friday before you posted v2 and actually had this ready to go Saturday or so, but some back-end stuff wasn't resolved until today.
diff --git a/scripts/config_whitelist.txt b/scripts/config_whitelist.txt index 71df6dbebde6..19b573c3d3f3 100644 --- a/scripts/config_whitelist.txt +++ b/scripts/config_whitelist.txt @@ -1334,7 +1334,6 @@ CONFIG_MTD_UBI_MODULE CONFIG_MULTI_CS CONFIG_MUSB_HOST CONFIG_MVEBU_MMC -CONFIG_MVGBE CONFIG_MVGBE_PORTS CONFIG_MVMFP_V2 CONFIG_MVS
Now that there are more boards defining this it can be removed from the whitelist. Signed-off-by: Chris Packham <judge.packham@gmail.com> --- scripts/config_whitelist.txt | 1 - 1 file changed, 1 deletion(-)