Re: linux-next: build warning after merge of the mac80211-next tree

Hi all, Just cc'ing the wireless list at Kalle's suggestion. On Wed, 9 May 2018 14:56:24 +1000 Stephen Rothwell <s...@canb.auug.org.au> wrote: > > Hi Johannes, > > After merging the mac80211-next tree, today's linux-next build (arm_multi > v7_defconfig) produced this warn

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

conflicts should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless

linux-next: Signed-off-by missing for commit in the wireless-drivers-next tree

Hi all, Commit 84226ca1c5d3 ("iwlwifi: mvm: support offload of AMSDU rate control") is missing a Signed-off-by from its author. -- Cheers, Stephen Rothwell pgpH_8cAXV1iy.pgp Description: OpenPGP digital signature

linux-next: build failure after merge of the mac80211-next tree

ell Dave when these trees meet in his tree. From: Stephen Rothwell <s...@canb.auug.org.au> Date: Tue, 12 Dec 2017 12:50:40 +1100 Subject: [PATCH] mt76: fix up for "mac80211: Add TXQ scheduling API" Signed-off-by: Stephen Rothwell <s...@canb.auug.org.au> --- drivers/net/wireles

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

ainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless/intel/iwlwifi/pcie/drv.c index ccd7c33c4c28,5ed89d

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

Hi all, On Thu, 24 Aug 2017 11:17:53 +1000 Stephen Rothwell <s...@canb.auug.org.au> wrote: > > IWL_DEBUG_DEV(dev, IWL_DL_LAR, > - "Ch. %d [%sGHz] %s%s%s%s%s%s%s%s%s(0x%02x) > reg_flags 0x%x: %s\n", > -

Re: pull-request: iwlwifi-next 2017-08-18

; this: > > > > "Ch. %d [%sGHz] %s%s%s%s%s%s%s%s%s%s%s%s(0x%02x) reg_flags 0x%x: %s\n" > > Thanks, I'll Cc Stephen because he most probably sees that conflict > tomorrow. Thanks for the heads up ... -- Cheers, Stephen Rothwell

linux-next: manual merge of the wireless-drivers-next tree with Linus' tree

upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell

linux-next: manual merge of the wireless-drivers-next tree with Linus' tree

ur tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless/intel/iwlwifi/mvm/rs.c index 8999a1199d60,44c873082a31.. --- a/

linux-next: manual merge of the wireless-drivers-next tree with Linus' tree

should be mentioned to your upstream maintainer when your tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless/intel/iwlwifi/i

Re: Adding nfc-next to linux-next

* successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. -- Cheers, Stephen Rothwell s...@canb.auug.org.au

linux-next: build warning after merge of the wireless-drivers tree

' may be used uninitialized in this function [-Wmaybe-uninitialized] mutex_unlock(>dev_init_lock); ^ Introduced by commit 6d0507a777fb ("brcmfmac: add parameter to pass error code in firmware callback") -- Cheers, Stephen Rothwell

Re: linux-next: build failure after merge of the wireless-drivers-next tree

Hi Dave, On Thu, 15 Jun 2017 12:08:08 -0400 (EDT) David Miller <da...@davemloft.net> wrote: > > From: Stephen Rothwell <s...@canb.auug.org.au> > Date: Tue, 13 Jun 2017 12:00:24 +1000 > > > On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell <s...@canb.auug.org.

Re: linux-next: build failure after merge of the wireless-drivers-next tree

Hi Dave, On Thu, 8 Jun 2017 12:27:59 +1000 Stephen Rothwell <s...@canb.auug.org.au> wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (x86_64 allmodconfig) failed like this: > > drivers/net/wireless/quantenna/qtnfmac/core.c: In function &g

Re: linux-next: build failure after merge of the wireless-drivers-next tree

Hi Kalle, On Thu, 08 Jun 2017 15:07:00 +0300 Kalle Valo <kv...@codeaurora.org> wrote: > > Stephen Rothwell <s...@canb.auug.org.au> writes: > > > On Wed, 7 Jun 2017 19:43:18 -0700 Igor Mitsyanko > > <igor.mitsyanko...@quantenna.com> wrote: > >&

Re: linux-next: build failure after merge of the wireless-drivers-next tree

imilar) when he merges the wireless-drivers-next tree into the net-next tree. I will keep applying the patch each day until then. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the wireless-drivers-next tree

from the net tree. I applied this merge fix patch for today. From: Stephen Rothwell <s...@canb.auug.org.au> Date: Thu, 8 Jun 2017 12:24:08 +1000 Subject: [PATCH] qtnfmac: fix up for "net: Fix inconsistent teardown and release of private netdev state." Signed-off-by: Stephen Rothwe

Re: [PATCH] staging: rtl8723bs: Add missing include to fix compile error

Hi Hans, On Mon, 10 Apr 2017 21:13:07 +0200 Hans de Goede <hdego...@redhat.com> wrote: > > As reported by Stephen Rothwell when merging staging-next, > drivers/staging/rtl8723bs/core/rtw_ieee80211.c does not compile due > to of_get_property not being declared. > > Ex

linux-next: build warning after merge of the wireless-drivers-next tree

e (otherwise it would be tested for). -- Cheers, Stephen Rothwell

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

ur tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless/ath/ath10k/mac.c index 717b2fad9a8a,db6ddf974d1d.. --- a/driv

linux-next: build warning after merge of the wireless-drivers-next tree

-- Cheers, Stephen Rothwell

linux-next: manual merge of the l2-mtd tree with the wireless-drivers-next tree

. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/mtd/devices/Kconfig index 64a248556d29,bf8238fb2e12.. --- a/drivers/mtd/devices/Kconfig +++ b/drivers

Re: linux-next: build failure after merge of the wireless-drivers-next tree

l2-mtd.git/commitdiff/0a526341fee054c1e2b9f0e4b2b424ae81707d4c > > It's a trivial conflict, so should we just let Linus work it out? I can > note it my MTD pull request, if wireless lands first. Linus and I should be able to cope. I will send my usual notification today. -- Cheers, Stephen Rothwell -- To un

linux-next: build failure after merge of the wireless-drivers-next tree

es->start, resource_size(res)); ^ Caused by commit 57d8f7dd2132 ("bcma: allow enabling serial flash support on non-MIPS SoCs") I have reverted that commit for today. -- Cheers, Stephen Rothwell -- To unsubscribe from this list: send the line "unsubscribe linux-wireles

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

ur tree is submitted for merging. You may also want to consider cooperating with the maintainer of the conflicting tree to minimise any particularly complex conflicts. -- Cheers, Stephen Rothwell diff --cc drivers/net/wireless/intel/iwlwifi/mvm/scan.c index 1cac10c5d818,fb25d9e41912..00

Re: linux-next: build warning after merge of the wireless-drivers-next tree

Hi all, On Fri, 8 Jul 2016 11:32:14 +1000 Stephen Rothwell <s...@canb.auug.org.au> wrote: > > After merging the wireless-drivers-next tree, today's linux-next build > (arm multi_v7_defconfig, x86_64 allmodconfig) produced this warning: > > drivers/net/wireless/m

linux-next: build warning after merge of the wireless-drivers-next tree

mit a9c790ba23eb ("mwifiex: factor out mwifiex_cancel_scan") interacting with commit 1d76250bd34a ("nl80211: support beacon report scanning") from the net-next (and mac80211-next) tree. This will need some merge fix patch ... please send me or Dave one. -- Cheers, Stephen Rothwell

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

ss@vger.kernel.org as a contact for the wireless-drivers and wireless-drivers-next trees. -- Cheers, Stephen Rothwell -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: linux-next inclusion request for mac80211

u (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. -- Cheer

Re: randconfig build error with next-20150303, in drivers/bcma/driver_pcie2.c

=2264fc857decd45798368f46861d9aecac23546f However, that commit is in next-20150304 and we still get the error (see, for example, http://kisskb.ellerman.id.au/kisskb/buildresult/12376688/). -- Cheers, Stephen Rothwells...@canb.auug.org.au pgptkI9Uoc1PO.pgp Description: OpenPGP digital