From: Johannes Berg
Date: Fri, 11 Oct 2019 10:57:35 +0200
> Let me try to be a bit "maintainer-of-the-day agnostic" ;-)
>
> I'll be going on vacation, but figured I'd at least get this
> stuff out. As usual, I ran the hwsim tests from wpa_s/hostapd
> and all looks fine, compilation also was OK.
From: Johannes Berg
Date: Tue, 1 Oct 2019 18:01:16 +0200
> Here's a list of fixes - the BHs disabled one has been reported
> multiple times, and the SSID/MBSSID ordering one has over-the-air
> security implementations.
>
> Please pull and let me know if there's any problem.
Pulled and build te
From: Johannes Berg
Date: Wed, 11 Sep 2019 15:06:03 +0200
> On Wed, 2019-09-11 at 16:03 +0300, Jouni Malinen wrote:
>> The Layer 2 Update frame is used to update bridges when a station roams
>> to another AP even if that STA does not transmit any frames after the
>> reassociation. This behavior w
From: Johannes Berg
Date: Wed, 11 Sep 2019 15:13:25 +0200
> As detailed below, here are some more changes for -next, almost
> certainly the final round since the merge window is around the
> corner now.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
From: Johannes Berg
Date: Thu, 29 Aug 2019 17:00:10 +0200
> We have just three more fixes now, and one of those is a driver fix
> because Kalle is on vacation and I'm covering for him in the meantime.
>
> Please pull and let me know if there's any problem.
Ok, pulled, thanks.
From: Johannes Berg
Date: Wed, 21 Aug 2019 12:04:23 +0200
> For -next, we have more changes, but as described in the tag
> they really just fall into a few groups of changes :-)
>
> Please pull and let me know if there's any problem.
Also pulled, thanks.
From: Johannes Berg
Date: Wed, 21 Aug 2019 12:00:03 +0200
> I have here for you a few fixes; three, to be specific. Nothing that
> warrants real discussion or urgency though.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
Hello everyone,
Tomorrow I will be letting Jakub Kicinski manage the net and net-next
GIT trees. So he will be integrating patches into GIT and doing git
pulls from people. He will alway keep the patchwork states up to
date, just like I do.
I completely expect everyone to give Jakub the same
From: Oliver Neukum
Date: Thu, 8 Aug 2019 11:32:03 +0200
> The function is called before the lock which is asserted was ever used.
> Just remove it.
>
> Reported-by: syzbot+74c65761783d66a9c...@syzkaller.appspotmail.com
> Signed-off-by: Oliver Neukum
Please CC: the appropriate driver maitaine
From: Johannes Berg
Date: Wed, 31 Jul 2019 17:50:56 +0200
> There's a fair number of changes here, so I thought I'd get them out.
> I've included two Intel driver cleanups because Luca is on vacation,
> I'm covering for him, and doing it all in one tree let me merge all
> of the patches at once (
From: Johannes Berg
Date: Wed, 31 Jul 2019 14:49:32 +0200
> We have few fixes, most importantly probably the NETIF_F_LLTX revert,
> we thought we were now more layered like VLAN or such since we do all
> of the queue control internally, but it caused problems, evidently not.
>
> Please pull and
From: Johannes Berg
Date: Sat, 20 Jul 2019 22:24:55 +0200
> Sorry, this really should've gone out much earlier, in partilar
> the vendor command fixes. Not much for now, more -next material
> will come later.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
From: Johannes Berg
Date: Fri, 28 Jun 2019 16:44:43 +0200
> Just a single patch still for the current RC cycle, I debated
> whether to send a pull request at all or just ask you to apply
> the patch, but did it this way now.
>
> Please pull and let me know if there's any problem.
Either way wor
From: Johannes Berg
Date: Fri, 14 Jun 2019 16:16:37 +0200
> And ... here's a -next pull request. Nothing really major here,
> see more details below.
>
> Please pull and let me know if there's any problem.
Pulled and build testing, thank you.
From: Johannes Berg
Date: Fri, 14 Jun 2019 15:50:41 +0200
> Here's a round of fixes for the current tree, things are all over
> and the only really important thing is the TDLS and MFP fix, both
> of which allow a security bypass in MFP.
>
> Please pull and let me know if there's any problem.
Pu
Please only bug fixes as we progress through the merge window.
I'll announce when net-next is open again.
Follow me on social media:
https://twitter.com/davem_dokebi
Thank you.
From: Kalle Valo
Date: Fri, 01 Mar 2019 16:55:59 +0200
> as Linus gave us one more week here are few more patches to net-next for
> 5.1. Please let me know if there are any problems.
Pulled, thanks Kalle.
From: Yue Haibing
Date: Fri, 22 Feb 2019 15:37:58 +0800
> From: YueHaibing
>
> KASAN report this:
. ..
> nfc_llcp_build_tlv will return NULL on fails, caller should check it,
> otherwise will trigger a NULL dereference.
>
> Reported-by: Hulk Robot
> Fixes: eda21f16a5ed ("NFC: Set MIU and RW
From: Herbert Xu
Date: Sat, 23 Feb 2019 13:30:47 +0800
> This patch fixes an uninitialised return value error in
> ila_xlat_nl_cmd_flush.
>
> Reported-by: Dan Carpenter
> Fixes: 6c4128f65857 ("rhashtable: Remove obsolete...")
> Signed-off-by: Herbert Xu
Applied, thanks Herbert.
From: Wen Yang
Date: Fri, 22 Feb 2019 15:15:42 +0800
> diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c
> index 8c431e0..89823f0 100644
> --- a/net/dsa/dsa2.c
> +++ b/net/dsa/dsa2.c
> @@ -613,7 +613,7 @@ static int dsa_switch_parse_ports_of(struct dsa_switch
> *ds,
> struct device_node *ports,
From: Kalle Valo
Date: Fri, 22 Feb 2019 17:01:03 +0200
> here's a pull request to net-next tree for 5.1, more info below. Do note
> that the diffstat again was wrong due to the wireless-drivers merge so I
> had to recreate it manually.
>
> Please let me know if there are any problems.
Pulled, t
From: Johannes Berg
Date: Fri, 22 Feb 2019 14:25:12 +0100
> Here's the promised update with the big multi-BSSID changes,
> which are related to HE (802.11ax) for which we also have some
> updates.
>
> Note that I took the liberty of including Herbert's rhashtable
> API removal, I merged net-next
From: Johannes Berg
Date: Fri, 22 Feb 2019 14:10:51 +0100
> So ... I thought there weren't going to be any more patches
> when I asked you to apply that mac80211 one, but now a few
> days later I still ended up with three that are current and
> possibly even stable material.
>
> Please pull and
From: Kalle Valo
Date: Mon, 18 Feb 2019 17:19:26 +0200
> here's one more pull request to net tree for 5.0. Please let me know if
> you have any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Mon, 18 Feb 2019 11:29:29 +0100
> From: Wei Yongjun
>
> spin_lock_bh() is used in table_path_del() but rcu_read_unlock()
> is used for unlocking. Fix it by using spin_unlock_bh() instead
> of rcu_read_unlock() in the error handling case.
>
> Fixes: b4c3fbe63601 ("mac8
From: Johannes Berg
Date: Fri, 15 Feb 2019 13:51:45 +0100
> It's clear things are winding down, this is basically just the stuff
> from Herbert that we've been discussing. I threw in a simple error
> path fix, mostly because it's simple :-)
>
> Please pull and let me know if there's any problem.
From: Johannes Berg
Date: Wed, 6 Feb 2019 10:07:21 +0100
> From: Johannes Berg
>
> When an rhashtable walk is done from softirq context, we rightfully
> get a lockdep complaint saying that we could get a softirq in the
> middle of a rehash, and thus deadlock on &ht->lock. This happened
> e.g.
From: Johannes Berg
Date: Tue, 12 Feb 2019 12:51:20 +0100
> We have few more fixes, mostly one-liners; two are bigger:
> * the speculation one, only because the function had multiple
>return points and that had to change, and
> * the peer measurement locking one, because I had to refactor
>
From: Johannes Berg
Date: Wed, 06 Feb 2019 09:15:15 +0100
> On Tue, 2019-02-05 at 15:37 +0100, Johannes Berg wrote:
>> From: Johannes Berg
>>
>> When an rhashtabl walk is done from irq/bh context, we rightfully
>> get a lockdep complaint saying that we could get a (soft-)IRQ in
>> the middle of
From: Kalle Valo
Date: Wed, 06 Feb 2019 09:17:10 +0200
> here's a pull request to net-next for 5.1, more info below. Please let
> me know if there are any problems.
Pulled, thanks Kalle!
From: Kalle Valo
Date: Mon, 04 Feb 2019 15:58:08 +0200
> here are fixes to net tree for 5.0, more info below. Please let me know
> if there are any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Fri, 1 Feb 2019 12:16:50 +0100
> Here's my next pull request for net-next. I wanted to include more,
> notably the multi-BSSID work that's going on now (multi-BSSID lets
> a single AP with a single beacon have multiple networks, rather than
> requiring a beacon for each
From: Johannes Berg
Date: Fri, 1 Feb 2019 11:17:43 +0100
> Two more fixes for the current cycle, one is a new bug introduced
> in 4.20, the other one seems to be much older.
>
> Please pull and let me know if there's any problem.
Pulled, thanks!
From: YueHaibing
Date: Tue, 29 Jan 2019 14:40:28 +0800
> gcc warning this:
> net/nfc/nci/hci.c:373:5:
> warning: variable 'status' set but not used [-Wunused-but-set-variable]
>
> It not used since commit d8cd37ed2fc8 ("NFC: nci: Fix improper
> management of HCI return code"), so can be removed
From: Johannes Berg
Date: Fri, 25 Jan 2019 20:34:57 +0100
> On Fri, 2019-01-25 at 11:04 -0800, David Miller wrote:
>>
>> > Dave, it looks like we're the only users of this right now,
>> > so let me know if you'd prefer I take it through my tree.
>>
From: Johannes Berg
Date: Fri, 25 Jan 2019 10:08:28 +0100
> From: Johannes Berg
>
> In typical cases, there's no need to pass both the maxattr
> and the policy array pointer, as the maxattr should just be
> ARRAY_SIZE(policy) - 1. Therefore, to be less error prone,
> just remove the maxattr arg
From: Johannes Berg
Date: Fri, 25 Jan 2019 14:20:40 +0100
> Here are 8 fixes for the current cycle, nothing that seems out of
> the ordinary.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
From: "Gustavo A. R. Silva"
Date: Sat, 22 Dec 2018 17:37:35 -0600
> I wonder if you can take this one too:
>
> https://lore.kernel.org/lkml/20181221212229.GA32635@embeddedor/
>
> It's pretty similar to the af_nfc one.
Sure, done.
From: "Gustavo A. R. Silva"
Date: Fri, 21 Dec 2018 15:47:53 -0600
> proto is indirectly controlled by user-space, hence leading to
> a potential exploitation of the Spectre variant 1 vulnerability.
>
> This issue was detected with the help of Smatch:
>
> net/nfc/af_nfc.c:42 nfc_sock_create() wa
From: Kalle Valo
Date: Thu, 20 Dec 2018 20:02:21 +0200
> here's a pull request to net-next for 4.21. More info in the signed
> below.
>
> As I have been too busy this cycle not all of these have been in
> linux-next, but most of them has been tested by the kbuild bot and the
> last few remaining
From: Kalle Valo
Date: Wed, 19 Dec 2018 16:34:02 +0200
> this a pull request to net tree for 4.20, more info below.
>
> Really sorry for sending a late request like this but I have been busy
> with other stuff and this just got delayed. These are pretty
> important fixes so I hope there's still
From: Johannes Berg
Date: Wed, 19 Dec 2018 10:30:33 +0100
> Last chance, I guess, but do have quite a long list of
> changes for -next, some of which I really should've
> sent earlier, sorry about that. See below for a brief
> summary in the tag, and of course the shortlog is also
> below.
>
> T
From: Johannes Berg
Date: Wed, 19 Dec 2018 09:49:41 +0100
> It's getting late in the cycle, so I don't know if you still want to
> take these in, but we have three fixes for kernel crashes we've seen
> at least here at Intel.
>
> Please pull and let me know if there's any problem.
Yes, I always
From: Johannes Berg
Date: Wed, 5 Dec 2018 15:29:34 +0100
> As per the below summary / shortlog, we have a few things
> that should still go into the current release.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes!
Your CC list is so huge that vger.kernel.org dropped all of your postings.
That CC list is not reasonable at all, trim it down to the most minimum
set. Probably 2 or 3 mailing lists, primarily netdev, and maybe a small
handful of specific developers.
Nothing more.
From: Kalle Valo
Date: Fri, 30 Nov 2018 15:33:29 +0200
> here's a pull request to net-next tree for 4.21, more info below. Please
> let me know if you have any problems.
Pulled, thank you Kalle.
From: Kalle Valo
Date: Tue, 20 Nov 2018 17:22:07 +0200
> here's a pull request to net tree for 4.20, more info below. Please let
> me know if there are any problems.
Pulled, thank you.
[ As I am trying to remove direct SKB list pointer accesses I am
committing this to net-next. If this causes a lot of grief I
can and will revert, just let me know. ]
Instead of direct SKB list pointer accesses.
The loops in this function had to be rewritten to accommodate this
more easily
From: Johannes Berg
Date: Fri, 12 Oct 2018 12:53:00 +0200
> From: Johannes Berg
>
> We already have BUILD_BUG_ON_ZERO() which I just hadn't found
> before, so we should use it here instead of open-coding another
> implementation thereof.
>
> Signed-off-by: Johannes Berg
> ---
> v2: remove all
From: Johannes Berg
Date: Fri, 12 Oct 2018 13:13:53 +0200
> Here's another set of updates. Note that there's a patch here
> (lib80211 skcipher removal to simplify the code) that will
> cause conflicts when merging with the crypto tree, the new
> code from this should be used. Please advise Greg/L
From: YueHaibing
Date: Mon, 8 Oct 2018 13:21:49 +
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/net/wireless/mediatek/mt76/mt76x0/pci.c: In function
> 'mt76x0e_register_device':
> drivers/net/wireless/mediatek/mt76/mt76x0/pci.c:107:8: warning:
> variable 'data' set but not u
From: Kalle Valo
Date: Sun, 07 Oct 2018 10:37:06 +0300
> another pull request to net-next for 4.20. I'm sending this a bit
> earlier than I prefer as I'm not sure if the merge window starts today
> or not. Not all of these patches have been in linux-next, and also the
> kbuild bot has been offlin
From: Johannes Berg
Date: Thu, 4 Oct 2018 21:43:54 +0200
> I got three more fixes submitted, and am sending those to you
> now in the hope of still getting them in, although all of the
> bugs are actually older than the current cycle.
>
> If there's a release on Sunday then I guess I won't care
From: Kalle Valo
Date: Mon, 01 Oct 2018 14:59:14 +0300
> here's a really small pull request to net tree for 4.19. More info below
> and please let me know if there are any problems.
Pulled, thank you.
From: Kalle Valo
Date: Tue, 02 Oct 2018 20:06:30 +0300
> here's the first pull request to net-next for 4.20. This is rather large
> due to mt76 refactoring and me not being able to send the pull request
> earlier, sorry about that.
>
> Most of this has been in linux-next for some time now so I'm
From: Johannes Berg
Date: Thu, 27 Sep 2018 13:18:50 +0200
> Here's another - unfortunately pretty large - set of fixes
> for the current cycle. The changes are pretty simple or even
> trivial though.
>
> Please pull and let me know if there's any problem.
Pulled.
If they are all legit fixes, h
From: Johannes Berg
Date: Mon, 3 Sep 2018 14:15:45 +0200
> This time around for mac80211 I have a larger than usual number of
> fixes, in part because Luca dumped our (Intel's) patches out after
> quite a while - we'll try to make sure this doesn't happen again.
>
> Shortlog below, as usual, ea
From: Johannes Berg
Date: Wed, 23 May 2018 14:14:31 +0200
> Here's a new version of the pull request for net-next, now
> with the stack size fixes included, which were the reason I
> withdrew my earlier one. Other things are also included all
> over the map.
>
> Please pull and let me know if th
From: Kalle Valo
Date: Tue, 22 May 2018 17:28:11 +0300
> here's a pull request to net tree for 4.17. Please let me know if you
> have any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Wed, 23 May 2018 11:47:57 +0200
> Just another handful of fixes as we wind down towards the
> merge window.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
Please don't tell me you will soon queue up a patch that
limits wiphy names to
From: Kalle Valo
Date: Thu, 17 May 2018 11:44:34 +0300
> here's a pull request to net-next for 4.18. I forgot to mention in the
> signed tag was that one id is added to include/linux/mmc/sdio_ids.h but
> that was acked by Ulf.
>
> I suspect hat because of my merge of wireless-drivers into
> wire
Linux Plumbers Networking Track CFP
This is a call for proposals for the networking track at the 2018
edition of the Linux Plumbers Conference which will be held in
Vancouver on November 13th and November 14th.
The LPC Networking Track is a community event, open to everyone, and
does not require
From: Johannes Berg
Date: Wed, 09 May 2018 23:29:37 +0200
> Hi,
>
> Sorry, scratch that.
>
> I forgot that this commit:
>
>> Toke Høiland-Jørgensen (3):
>
>> cfg80211: Expose TXQ stats and parameters to userspace
>
> caused a bunch of "too much stack" warnings - I should put in at leas
From: Johannes Berg
Date: Wed, 9 May 2018 21:36:12 +0200
> We just have a few fixes this time around.
>
> Please pull and let me know if there's any problem.
Pulled, thank you!
From: Kalle Valo
Date: Thu, 26 Apr 2018 13:12:54 +0300
> here's a pull request to net tree, more info below. Please let me know
> if you have any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Thu, 19 Apr 2018 17:26:57 +0200
> On Thu, 2018-04-19 at 08:25 -0700, Ben Greear wrote:
>>
>> Maybe this could be in followup patches? It's going to touch a lot of files,
>> and might be hell to get merged all at once, and I've never used spatch, so
>> just maybe someon
From: Masanari Iida
Date: Wed, 4 Apr 2018 20:53:33 +0900
> After 03fe2debbb2771fb90881e merged during 4.17 marge window,
> I start to see following warning during "make xmldocs"
>
> ./include/net/mac80211.h:2083: warning: bad line: >
>
> Replace ">" with "*" fix the issue.
>
> Signed-off-by:
From: Kalle Valo
Date: Thu, 29 Mar 2018 16:21:44 +0300
> here's a pull request to net-next for 4.17. If the merge window starts
> on Sunday this will be the last pull request. Do note that I pulled
> wireless-drivers into wireless-drivers-next as iwlwifi needed some
> patches.
>
> Please let me
From: Johannes Berg
Date: Thu, 29 Mar 2018 15:10:02 +0200
> Last update for -next, I guess, but I wanted to get the ETSI adaptivity
> requirements code and the eapol-over-nl80211 thing out - both have been
> around for a while. A number of other smaller things are also there, of
> course.
>
> Pl
From: Kirill Tkhai
Date: Thu, 29 Mar 2018 19:20:23 +0300
> The series introduces fine grained rw_semaphore, which will be used
> instead of rtnl_lock() to protect net_namespace_list.
>
> This improves scalability and allows to do non-exclusive sleepable
> iteration for_each_net(), which is enoug
Applied.
From: Kalle Valo
Date: Sat, 24 Mar 2018 14:30:01 +0200
> here's the first pull request to net-next for 4.17. What's special here
> is the addition of a new bluetooth driver, but that's been acked by
> Marcel. Also we add a new include file to include/net because of that.
>
> Please let me know i
From: Kalle Valo
Date: Sat, 24 Mar 2018 13:03:13 +0200
> This is a pull request to the net tree for 4.16. I'm not planning to
> send anything more in this cycle for 4.16, unless something really major
> comes up.
>
> Please let me know if you have any problems.
Pulled.
From: Johannes Berg
Date: Wed, 21 Mar 2018 13:06:54 +0100
> Another few fixes - one for hwsim, so not really all that interesting,
> and two patches to work around an ath9k_htc problem.
>
> Note that I pulled your net tree today, so you may need to be careful
> to not fast-forward if you don't m
From: Joe Perches
Date: Mon, 12 Mar 2018 08:07:12 -0700
> skb_copy_expand without __GFP_NOWARN already does a dump_stack
> on OOM so these messages are redundant.
>
> Signed-off-by: Joe Perches
Ok, applied to net-next, thanks.
From: Kalle Valo
Date: Thu, 08 Mar 2018 17:18:29 +0200
> here's a pull requsest to net tree for 4.16. Since the merge window I
> have had some clannges to keep up with some patches but catching up now.
>
> There should be nothing special here but please let me know if you have
> any problems.
P
From: Geert Uytterhoeven
Date: Fri, 2 Mar 2018 14:43:23 +0100
> Signed-off-by: Geert Uytterhoeven
I'll let the trivial tree pick this up.
From: Johannes Berg
Date: Fri, 2 Mar 2018 10:06:54 +0100
> Like before... Thanks for pulling net into net-next, the Add-BA patch
> below would otherwise not really be possible :-)
No problem.
> The only sort of interesting thing is the fast-RX improvements from
> Felix, they help on routers wh
From: Johannes Berg
Date: Fri, 2 Mar 2018 10:04:46 +0100
> Just a few more patches, but I'll be travelling over the next
> week and probably won't be able to send things to you then.
>
> Please pull and let me know if there's any problem.
Ok, pulled, safe travels.
Thanks!
From: Johannes Berg
Date: Fri, 23 Feb 2018 12:29:39 +0100
> On Thu, 2018-02-22 at 15:19 -0500, David Miller wrote:
>>
>> Pulled, thank you!
>
> Thanks. I just realized that I have a patch pending for -next that
> depends another commit in net/mac80211 (or would otherwis
From: Johannes Berg
Date: Thu, 22 Feb 2018 21:16:18 +0100
> Wireless is slow ... but we're preparing for HE (802.11ax),
> so I guess soon we'll have a big chunk of work coming :-)
I wondered where you guys have been hiding :-)
> Please pull and let me know if there's any problem.
Pulled, thank
From: Johannes Berg
Date: Thu, 22 Feb 2018 21:08:39 +0100
> A bunch of fixes, including the nla_put_string() issue
> just in from Kees. Otherwise nothing really super urgent
> or interesting.
>
> Please pull and let me know if there's any problem.
Pulled.
Thanks for taking care of that NLA_STR
From: Denys Vlasenko
Date: Mon, 12 Feb 2018 20:00:20 +0100
> Changes since v1:
> Added changes in these files:
> drivers/infiniband/hw/usnic/usnic_transport.c
> drivers/staging/lustre/lnet/lnet/lib-socket.c
> drivers/target/iscsi/iscsi_target_login.c
> drivers/vhost/net.c
> fs
From: Denys Vlasenko
Date: Mon, 12 Feb 2018 15:15:18 +0100
> Before:
> All these functions either return a negative error indicator,
> or store length of sockaddr into "int *socklen" parameter
> and return zero on success.
>
> "int *socklen" parameter is awkward. For example, if caller does not
From: Kalle Valo
Date: Thu, 08 Feb 2018 19:54:15 +0200
> first set of fixes for 4.16, unusually many when the merge window hasn't
> even closed yet. Especially the ssb fix is important so I hope there's
> still time to get this to 4.16-rc1. As you can see from the diffstat
> there's one PCI id ad
From: Kalle Valo
Date: Fri, 26 Jan 2018 19:04:29 +0200
> this is a pull request to net-next for 4.16, more info in the signed
> tag below. Please let me know if you have any problems.
Pulled, thanks Kalle.
From: Kalle Valo
Date: Fri, 26 Jan 2018 18:33:33 +0200
> this is a pull request to the net tree for 4.15. I hate to do late pull
> requests like this but today Sven Joachim found a serious regression in
> one of ssb patches, I hope there's still enough time to get this to
> 4.15.
>
> But if it's
From: Johannes Berg
Date: Mon, 22 Jan 2018 14:15:00 +0100
> A few more (only four, really) changes have come in, so I figured
> since the merge window hasn't opened yesterday, I'd still send them
> to you.
>
> Please pull and let me know if there's any problem.
I had to resolve a conflict in ma
From: Kalle Valo
Date: Fri, 19 Jan 2018 10:59:33 +0200
> a pull request to net-next tree for 4.16. This should be the last pull
> request in this cycle, unless Linus releases -rc9 of course. Only few
> patches so should be an easy one. Please let me know if there are any
> problems.
Pulled, than
From: Kalle Valo
Date: Wed, 17 Jan 2018 16:30:21 +0200
> here are few more important fixes to the net tree for 4.15, I hope they
> still make it. Please let me know if there are any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Tue, 16 Jan 2018 23:20:22 +0100
> From: Johannes Berg
>
> Fix two places where the structure isn't initialized to zero,
> and thus can't be filled properly by the driver.
>
> Fixes: 4a4b8169501b ("cfg80211: Accept multiple RSSI thresholds for CQM")
> Fixes: 9930380f0b
From: Johannes Berg
Date: Mon, 15 Jan 2018 11:51:53 +0100
> I know this comes last minute, so if it doesn't make it then
> I guess we can live with that, but I got the earliest of the
> patches here on Wednesday last week, and that was the most
> uninteresting one - the others didn't come in unti
From: Kalle Valo
Date: Sat, 13 Jan 2018 12:33:43 +0200
> this is a pull request to net-next tree for 4.16, more info in the
> signed tag below. I'm not expecting any problems but please let me know
> if you have any.
Pulled, thanks Kalle.
From: Kalle Valo
Date: Tue, 09 Jan 2018 14:59:37 +0200
> My first pull request in 2018 so Happy New Year!
Happy New Year to you as well :)
> This is for 4.15 to the net tree. Only two fixes this time so should be
> an easy pull.
>
> This is quite late due to the holidays but it has been pretty
From: Johannes Berg
Date: Thu, 4 Jan 2018 15:56:31 +0100
> It's probably getting quite late for the current cycle, but
> these fixes seemed important enough to send them to you
> separately anyway.
>
> Please pull and let me know if there's any problem.
Sure, no problem, pulled.
From: Kalle Valo
Date: Mon, 18 Dec 2017 16:17:24 +0200
> a pull request for 4.16 to net-next tree. This is a big one, but on the
> other hand most of the stuff here has been some time on linux-next so
> hopefully there are no nasty surprises. Even though Arnd just send a
> patch[1] five minutes a
From: Johannes Berg
Date: Tue, 19 Dec 2017 10:57:09 +0100
> Other work has been hectic, and I got caught by rc4. We still
> have a few more fixes though - and more build issues were
> reported.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
From: Richard Schütz
Date: Mon, 11 Dec 2017 14:51:33 +0100
> as per netdev-FAQ.txt I'm requesting the submission of commit
> 57629915d568c522ac1422df7bba4bee5b5c7a7c ("mac80211: Fix addition of
> mesh configuration element") to stable. Because of automatic selection
> commit 76f43b4c0a9337af22827
From: Johannes Berg
Date: Mon, 11 Dec 2017 10:52:35 +0100
> Three fixes, two related to build issues with the new regdb stuff,
> and one for some patch overlap problem that caused locking to be
> missing which in turn caused lots of warnings.
>
> Please pull and let me know if there's any proble
From: Kalle Valo
Date: Fri, 08 Dec 2017 16:32:16 +0200
> this is a pull request to net tree for 4.15, more info in the signed tag
> below. All small fixes and not really expecting any problems, but please
> let me know if you have any.
Pulled, thanks Kalle.
1 - 100 of 480 matches
Mail list logo
