Skip to contentSkip to conversation

Remove CONFIG_MVGBE from config_whitelist.txt

PATCH In review Chris Packham 3 participants 5 messages May 16, 2018 – May 29, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Remove CONFIG_MVGBE from config_whitelist.txt

Now that there are more boards defining this it can be removed from the whitelist.

---

 scripts/config_whitelist.txt | 1 -
 1 file changed, 1 deletion(-)
scripts/config_whitelist.txt +0 -1
index 71df6dbebde6..19b573c3d3f3 100644
@@ -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
Signature · 1 line
2.17.0
#2 lore raw
In reply to Chris Packham
Quoted 5 lines · Chris Packham

Now that there are more boards defining this it can be removed from the whitelist.

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180528/c9c8cfda/attachment.sig>
#3 lore raw

Hi Tom,

Quoted 9 lines · Tom Rini
Quoted 5 lines · Chris Packham

Now that there are more boards defining this it can be removed from the whitelist.

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:?

#4 lore raw
Quoted 11 lines · Chris Packham

Hi Tom,

Quoted 7 lines · Tom Rini
Quoted 5 lines · Chris Packham

Now that there are more boards defining this it can be removed from the whitelist.

Quoted 7 lines
Quoted 1 line

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.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180528/087299cc/attachment.sig>