patches: fix path in name_assign_type patch
PATCH 1/1 patches: fix path in name_assign_type patch
Patch for brcmfmac need update path as it now resides under the broadcom vendor directory.
--- .../network/0055-name_assign_type/brcmfmac.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch +2 -2
@@ -1,5 +1,5 @@ ---- a/drivers/net/wireless/brcm80211/brcmfmac/p2p.c -+++ b/drivers/net/wireless/brcm80211/brcmfmac/p2p.c +--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c ++++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c @@ -2204,7 +2204,9 @@ struct wireless_dev *brcmf_p2p_add_vif(s }
Signature · 4 lines
1.9.1 -- To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 14 lines · Arend van Spriel
Patch for brcmfmac need update path as it now resides under the broadcom vendor directory.
Signed-off-by Arend van Spriel <[email protected]>--- .../network/0055-name_assign_type/brcmfmac.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch +0
-0
patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch line 5
Quoted 7 lines
patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch +2
-2@@ -1,5 +1,5 @@ ---- a/drivers/net/wireless/brcm80211/brcmfmac/p2p.c -+++ b/drivers/net/wireless/brcm80211/brcmfmac/p2p.c +--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c ++++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c @@ -2204,7 +2204,9 @@ struct wireless_dev *brcmf_p2p_add_vif(s }
I will do this for all patches at once, but thanks.
Is it ok to replace the b43, b43legacy and brcm80211 by this single line? drivers/net/wireless/broadcom/
Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 5 lines
Is it ok to replace the b43, b43legacy and brcm80211 by this single line?
drivers/net/wireless/broadcom/
You mean in a single patch? I generally considered each file (or at least driver) separately so you could restrict copy-list to it.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 8 lines · Johannes Berg
Quoted 5 lines
Is it ok to replace the b43, b43legacy and brcm80211 by this single line?
drivers/net/wireless/broadcom/You mean in a single patch? I generally considered each file (or at least driver) separately so you could restrict copy-list to it.
There is option to do:
drivers/net/wireless/broadcom/Kconfigdrivers/net/wireless/broadcom/Makefiledrivers/net/wireless/broadcom/b43drivers/net/wireless/broadcom/b43legacydrivers/net/wireless/broadcom/brcm80211
Or (as Hauke suggests):
drivers/net/wireless/broadcom/
To restrict the copy-list the first option would be preferred.
Regards,
Arend
Quoted 4 lines
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 9 lines · Arend van Spriel
Quoted 1 line
Quoted 1 line
drivers/net/wireless/broadcom/
drivers/net/wireless/broadcom/Kconfigdrivers/net/wireless/broadcom/Makefiledrivers/net/wireless/broadcom/b43drivers/net/wireless/broadcom/b43legacydrivers/net/wireless/broadcom/brcm80211
Quoted 6 lines
Or (as Hauke suggests):
drivers/net/wireless/broadcom/To restrict the copy-list the first option would be preferred.
Oh, you meant for the copy-list?
I thought upstream backports just shipped a single copy-list line "ddrivers/net/wireless/"?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 14 lines · Johannes Berg
Quoted 13 lines · Arend van Spriel
Quoted 2 lines
Quoted 2 lines
drivers/net/wireless/broadcom/
drivers/net/wireless/broadcom/Kconfigdrivers/net/wireless/broadcom/Makefiledrivers/net/wireless/broadcom/b43drivers/net/wireless/broadcom/b43legacydrivers/net/wireless/broadcom/brcm80211Or (as Hauke suggests):
drivers/net/wireless/broadcom/
Quoted 7 lines
Quoted 2 lines
To restrict the copy-list the first option would be preferred.
Oh, you meant for the copy-list?
I thought upstream backports just shipped a single copy-list line "ddrivers/net/wireless/"?
Nope. It is:
# 802.11drivers/net/wireless/Kconfigdrivers/net/wireless/Makefile
It looks for subfolders and modifies the Kconfig and Makefile for the ones missing (comment out).
Regards,
Arend
Quoted 2 lines
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 29 lines · Arend van Spriel
Quoted 14 lines · Johannes Berg
Quoted 13 lines · Arend van Spriel
Quoted 2 lines
Quoted 2 lines
drivers/net/wireless/broadcom/
drivers/net/wireless/broadcom/Kconfigdrivers/net/wireless/broadcom/Makefiledrivers/net/wireless/broadcom/b43drivers/net/wireless/broadcom/b43legacydrivers/net/wireless/broadcom/brcm80211Or (as Hauke suggests):
drivers/net/wireless/broadcom/Quoted 7 lines
Quoted 2 lines
To restrict the copy-list the first option would be preferred.
Oh, you meant for the copy-list?
I thought upstream backports just shipped a single copy-list line "ddrivers/net/wireless/"?
Nope. It is:
# 802.11
drivers/net/wireless/Kconfigdrivers/net/wireless/Makefile
Quoted 8 lines
It looks for subfolders and modifies the
KconfigandMakefilefor the ones missing (comment out).Regards,
ArendQuoted 2 lines
johannes
Arend is right I was asking if you would like:drivers/net/wireless/broadcom/Kconfigdrivers/net/wireless/broadcom/Makefiledrivers/net/wireless/broadcom/b43drivers/net/wireless/broadcom/b43legacydrivers/net/wireless/broadcom/brcm80211
or this:drivers/net/wireless/broadcom/
or this:drivers/net/wireless/
for the copy-list file.
This is not just about the Broadcom driver I would do it in the same way for all wifi driver.
Do both of you replace the copy-list file in your internal versions?
Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 3 lines · Hauke Mehrtens
Do both of you replace the copy-list file in your internal versions?
I think Arend said he did, and I certainly do that too. I actually just have my own and run the gentree/git-tracker scripts with the right commandline parameter.
So I think
drivers/net/wireless/
makes most sense since that requires no maintenance?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
Quoted 24 lines · Hauke Mehrtens
Quoted 14 lines · Arend van Spriel
Patch for brcmfmac need update path as it now resides under the broadcom vendor directory.
Signed-off-by Arend van Spriel <[email protected]>--- .../network/0055-name_assign_type/brcmfmac.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch +0
-0patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch line 5
Quoted 7 lines
patches/collateral-evolutions/network/0055-name_assign_type/brcmfmac.patch +2
-2@@ -1,5 +1,5 @@ ---- a/drivers/net/wireless/brcm80211/brcmfmac/p2p.c -+++ b/drivers/net/wireless/brcm80211/brcmfmac/p2p.c +--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c ++++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/p2p.c @@ -2204,7 +2204,9 @@ struct wireless_dev *brcmf_p2p_add_vif(s }I will do this for all patches at once, but thanks.
Quoted 2 lines
Is it ok to replace the b43, b43legacy and brcm80211 by this single line?
drivers/net/wireless/broadcom/
Fine by me. I have my own copy-list to only deal with brcm80211.
Regards,
Arend
Quoted 4 lines
Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in
--
To unsubscribe from this list: send the line "unsubscribe backports" in