linux-next: manual merge of the wireless-next tree with the wireless tree

2014-11-24 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/iwl-fw.h between commit 5ac6c72e5944 ("iwlwifi: mvm: check TLV flag before trying to use hotspot firmware commands") from the wireless tree and commit 77c5d7eff790 ("iwlwifi: mvm: add TDLS

linux-next: manual merge of the wireless-next tree with the wireless tree

2014-11-24 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/iwl-fw.h between commit 5ac6c72e5944 (iwlwifi: mvm: check TLV flag before trying to use hotspot firmware commands) from the wireless tree and commit 77c5d7eff790 (iwlwifi: mvm: add TDLS

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Yeoh Chun-Yeow
>> I think the above is correct, the pre_value assignment with 1/++ and >> chsw_init moved into another function in Bob's patch. Bob? > > The quoted resolution looks right to me. But, I think the patch > in question was actually Chun-yeow's so I'm not sure my opinion > counts :) Yes, it is

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Bob Copeland
On Tue, Dec 03, 2013 at 05:09:43PM +0100, Johannes Berg wrote: > > > diff --cc net/mac80211/util.c > > > index 9f9b9bd3fd44,06265d7f8cc3.. > > > --- a/net/mac80211/util.c > > > +++ b/net/mac80211/util.c > > > @@@ -2457,9 -2481,13 +2479,8 @@@ int ieee80211_send_action_csa(struct ie > >

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Johannes Berg
On Tue, 2013-12-03 at 15:52 +, John W. Linville wrote: > > Today's linux-next merge of the wireless-next tree got a conflict in > > net/mac80211/util.c between commit 3f718fd8401d ("mac80211: fix the mesh > > channel switch support") from the wireless tree and commit ca91dc97b8a0 > >

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread John W. Linville
On Tue, Dec 03, 2013 at 11:20:32AM +1100, Stephen Rothwell wrote: > Hi John, > > Today's linux-next merge of the wireless-next tree got a conflict in > net/mac80211/util.c between commit 3f718fd8401d ("mac80211: fix the mesh > channel switch support") from the wireless tree and commit

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread John W. Linville
On Tue, Dec 03, 2013 at 11:20:32AM +1100, Stephen Rothwell wrote: Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/util.c between commit 3f718fd8401d (mac80211: fix the mesh channel switch support) from the wireless tree and commit ca91dc97b8a0

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Johannes Berg
On Tue, 2013-12-03 at 15:52 +, John W. Linville wrote: Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/util.c between commit 3f718fd8401d (mac80211: fix the mesh channel switch support) from the wireless tree and commit ca91dc97b8a0 (mac80211: use

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Bob Copeland
On Tue, Dec 03, 2013 at 05:09:43PM +0100, Johannes Berg wrote: diff --cc net/mac80211/util.c index 9f9b9bd3fd44,06265d7f8cc3.. --- a/net/mac80211/util.c +++ b/net/mac80211/util.c @@@ -2457,9 -2481,13 +2479,8 @@@ int ieee80211_send_action_csa(struct ie

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-03 Thread Yeoh Chun-Yeow
I think the above is correct, the pre_value assignment with 1/++ and chsw_init moved into another function in Bob's patch. Bob? The quoted resolution looks right to me. But, I think the patch in question was actually Chun-yeow's so I'm not sure my opinion counts :) Yes, it is correct. The

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-02 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/util.c between commit 3f718fd8401d ("mac80211: fix the mesh channel switch support") from the wireless tree and commit ca91dc97b8a0 ("mac80211: use put_unaligned_le16 for precedence value in mesh") from the

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-12-02 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/util.c between commit 3f718fd8401d (mac80211: fix the mesh channel switch support) from the wireless tree and commit ca91dc97b8a0 (mac80211: use put_unaligned_le16 for precedence value in mesh) from the

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-18 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 ("iwlwifi: pcie: disable L1 Active after pci_enable_device") from the wireless tree and commit 6965a3540a4b ("iwlwifi: pcie: don't swallow error

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-18 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 (iwlwifi: pcie: disable L1 Active after pci_enable_device) from the wireless tree and commit 6965a3540a4b (iwlwifi: pcie: don't swallow error

RE: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-12 Thread Berg, Johannes
> I think I have this slightly different in wireless-testing. Johannes, please > review and advise... > > Today's linux-next merge of the wireless-next tree got a conflict in > > drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 > > ("iwlwifi: pcie: disable L1 Active after

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-12 Thread John W. Linville
I think I have this slightly different in wireless-testing. Johannes, please review and advise... John On Mon, Aug 12, 2013 at 11:53:27AM +1000, Stephen Rothwell wrote: > Hi John, > > Today's linux-next merge of the wireless-next tree got a conflict in >

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-12 Thread John W. Linville
I think I have this slightly different in wireless-testing. Johannes, please review and advise... John On Mon, Aug 12, 2013 at 11:53:27AM +1000, Stephen Rothwell wrote: Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c

RE: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-12 Thread Berg, Johannes
I think I have this slightly different in wireless-testing. Johannes, please review and advise... Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 (iwlwifi: pcie: disable L1 Active after

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-11 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 ("iwlwifi: pcie: disable L1 Active after pci_enable_device") from thewireless tree and commit f2532b04b2ec ("iwlwifi: pcie: don't disable L1 for

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-08-11 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/iwlwifi/pcie/trans.c between commit eabc4ac5d760 (iwlwifi: pcie: disable L1 Active after pci_enable_device) from thewireless tree and commit f2532b04b2ec (iwlwifi: pcie: don't disable L1 for newest

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-06-07 Thread Sujith Manoharan
Stephen Rothwell wrote: > Today's linux-next merge of the wireless-next tree got a conflict in > drivers/net/wireless/ath/ath9k/Kconfig between commit 8bb7f167a12a > ("ath9k: Use minstrel rate control by default") from the wireless tree > and commit cf657a2bc50d ("ath9k: Remove MAC_DEBUG") from

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2013-06-07 Thread Sujith Manoharan
Stephen Rothwell wrote: Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/ath/ath9k/Kconfig between commit 8bb7f167a12a (ath9k: Use minstrel rate control by default) from the wireless tree and commit cf657a2bc50d (ath9k: Remove MAC_DEBUG) from the

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-06-06 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/ath/ath9k/Kconfig between commit 8bb7f167a12a ("ath9k: Use minstrel rate control by default") from the wireless tree and commit cf657a2bc50d ("ath9k: Remove MAC_DEBUG") from the wireless-next tree.

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-06-06 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/ath/ath9k/Kconfig between commit 8bb7f167a12a (ath9k: Use minstrel rate control by default) from the wireless tree and commit cf657a2bc50d (ath9k: Remove MAC_DEBUG) from the wireless-next tree. I

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-03-25 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/sta_info.c between commit 27a737ff7cb0 ("mac80211: always synchronize_net() during station removal") from the wireless tree and commits 3b8d9c290364 ("mac80211: remove underscores from some key functions")

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-03-25 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/sta_info.c between commit 27a737ff7cb0 (mac80211: always synchronize_net() during station removal) from the wireless tree and commits 3b8d9c290364 (mac80211: remove underscores from some key functions) and

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-03-11 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/nfc/llcp/llcp.c between commit 3536da06db0b ("NFC: llcp: Clean local timers and works when removing a device") from the wireless tree and commits d9b8d8e19b07 ("NFC: llcp: Service Name Lookup netlink interface") and

linux-next: manual merge of the wireless-next tree with the wireless tree

2013-03-11 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/nfc/llcp/llcp.c between commit 3536da06db0b (NFC: llcp: Clean local timers and works when removing a device) from the wireless tree and commits d9b8d8e19b07 (NFC: llcp: Service Name Lookup netlink interface) and

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2012-11-15 Thread Arend van Spriel
On 11/15/2012 03:17 AM, Stephen Rothwell wrote: Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit d61f978b8f26 ("brcmfmac: fix typo in CONFIG_BRCMISCAN") from the tree and commit f07998959d57

Re: linux-next: manual merge of the wireless-next tree with the wireless tree

2012-11-15 Thread Arend van Spriel
On 11/15/2012 03:17 AM, Stephen Rothwell wrote: Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit d61f978b8f26 (brcmfmac: fix typo in CONFIG_BRCMISCAN) from the tree and commit f07998959d57

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-11-14 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit d61f978b8f26 ("brcmfmac: fix typo in CONFIG_BRCMISCAN") from the tree and commit f07998959d57 ("brcmfmac: remove obsolete i-scan and clean up related

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-11-14 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit d61f978b8f26 (brcmfmac: fix typo in CONFIG_BRCMISCAN) from the tree and commit f07998959d57 (brcmfmac: remove obsolete i-scan and clean up related

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-10-21 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/mlme.c between commit 3a40414f826a ("mac80211: connect with HT20 if HT40 is not permitted") from the wireless tree and commit 04ecd2578e71 ("mac80211: track needed RX chains for channel contexts") from the

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-10-21 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit 3e4f319dacc6 ("brcmfmac: fix end of loop check (signedness bug)") from the wireless tree and commit 81118d165811 ("brcmfmac: Using zero instead of

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-10-21 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in drivers/net/wireless/brcm80211/brcmfmac/wl_cfg80211.c between commit 3e4f319dacc6 (brcmfmac: fix end of loop check (signedness bug)) from the wireless tree and commit 81118d165811 (brcmfmac: Using zero instead of NULL)

linux-next: manual merge of the wireless-next tree with the wireless tree

2012-10-21 Thread Stephen Rothwell
Hi John, Today's linux-next merge of the wireless-next tree got a conflict in net/mac80211/mlme.c between commit 3a40414f826a (mac80211: connect with HT20 if HT40 is not permitted) from the wireless tree and commit 04ecd2578e71 (mac80211: track needed RX chains for channel contexts) from the