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,
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.
>
>
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
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
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
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"
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
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
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
>
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
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
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.
>
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
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
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
>
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.
From: Johannes Berg <johan...@sipsolutions.net>
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 co
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
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
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
>
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
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
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
>
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
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
>
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
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 -
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
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
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
>
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
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
>
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
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.
From: David Ahern
Date: Tue, 5 Dec 2017 11:15:29 -0700
> Is the patch I sent as an attachment good or should I re-send
> standalone? (don't see it in patchwork)
Patchwork has been wonky laterly, please resubmit as a fresh
email for rewiew.
Thanks.
From: Johannes Berg <johan...@sipsolutions.net>
Date: Tue, 05 Dec 2017 18:30:10 +0100
> On Tue, 2017-12-05 at 11:41 -0500, David Miller wrote:
>>
>> There is no reasonable interpretation for what that application is
>> doing, so I think we can safely call that case a
From: David Ahern <dsah...@gmail.com>
Date: Tue, 5 Dec 2017 09:41:21 -0700
> On 12/5/17 9:34 AM, Johannes Berg wrote:
>> On Tue, 2017-12-05 at 11:31 -0500, David Miller wrote:
>>>
>>>> We could try to fix up the big endian problem here, but we
>>>>
From: Johannes Berg <johan...@sipsolutions.net>
Date: Tue, 05 Dec 2017 17:34:21 +0100
> On Tue, 2017-12-05 at 11:31 -0500, David Miller wrote:
>>
>> > We could try to fix up the big endian problem here, but we
>> > don't know *how* userspace misbehaved - if usi
From: Johannes Berg
Date: Sat, 2 Dec 2017 21:23:31 +0100
> From: Johannes Berg
>
> This netlink type is used only for backwards compatibility
> with broken userspace that used the wrong size for a given
> u8 attribute, which is now rejected.
From: Johannes Berg
Date: Mon, 27 Nov 2017 11:32:56 +0100
> Here are a few more fixes, one of which fixes the crash Florian
> reported which I think is the same that zero-day reported.
>
> Please pull and let me know if there's any problem.
Pulled, thanks Johannes.
From: Kalle Valo
Date: Wed, 22 Nov 2017 17:27:22 +0200
> here's the first pull request to net tree for 4.15. Please let me know
> if there are any problems.
Pulled, thanks Kalle!
From: Johannes Berg <johan...@sipsolutions.net>
Date: Tue, 21 Nov 2017 12:24:32 +0100
> On Tue, 2017-11-21 at 20:17 +0900, David Miller wrote:
>> From: Johannes Berg <johan...@sipsolutions.net>
>> Date: Mon, 20 Nov 2017 17:06:44 +0100
>>
>> > ssh://ko
From: Johannes Berg
Date: Mon, 20 Nov 2017 17:06:44 +0100
> ssh://korg/pub/scm/linux/kernel/git/jberg/mac80211.git
> tags/mac80211-for-davem-2017-11-20
That's an awesome URL, but I don't think I'll be able to pull
from it :-)
From: Kalle Valo
Date: Sat, 11 Nov 2017 15:03:14 +0200
> some more patches to net-next for v4.15. Even though I applied the last
> patch only on Saturday morning, all these have been tested by kbuild bot
> and most of them should also be in linux-next. Please let me know if
From: Kalle Valo
Date: Tue, 31 Oct 2017 17:19:24 +0200
> here's a pull request to net tree for 4.14. Due to the ath10k security
> issue I would like to get this to 4.14 still.
>
> Please let me know if there are any problems.
Pulled, thanks a lot.
From: Johannes Berg
Date: Wed, 25 Oct 2017 16:03:42 +0200
> Here are a few more fixes for net, we started comprehensive testing
> for the security issues and found that the problem wasn't addressed
> in TKIP, so that's included, along with a handful other fixes.
>
>
From: Kalle Valo
Date: Wed, 18 Oct 2017 12:42:31 +0300
> this for 4.15 stream to net-next tree. Please let me know if there are
> any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Mon, 16 Oct 2017 17:09:53 +0200
> From: Johannes Berg
>
> It seems that it's possible to toggle NETLINK_F_EXT_ACK
> through setsockopt() while another thread/CPU is building
> a message inside netlink_ack(), which
From: Johannes Berg
Date: Mon, 16 Oct 2017 16:57:49 +0200
> From: Johannes Berg
>
> When netlink_ack() reports an allocation error to the sending
> socket, there's no need to look up the sending socket since
> it's available in the SKB's CB.
From: Johannes Berg
Date: Fri, 13 Oct 2017 17:53:31 +0200
> Sorry for the quick succession - there were a few issues with
> the last pull request that only got noticed now, so I'm fixing
> those here.
>
> Please pull and let me know if there's any problem.
No
From: Kalle Valo
Date: Fri, 13 Oct 2017 10:25:14 +0300
> here's a pull request to net tree, more info in the signed tag below.
> Please let me know if there are any problems.
Pulled, thanks Kalle.
From: Johannes Berg
Date: Wed, 11 Oct 2017 14:36:12 +0200
> Here's a -next pull request. The only bigger thing here is the
> addition of the regulatory database as firmware, which will
> allow us to - over time - get rid of CRDA, as well as having
> the option of
From: Kees Cook
Date: Mon, 9 Oct 2017 17:10:32 -0700
> Several timer users needlessly reset their .function/.data fields during
> their timer callback, but nothing else changes them. Some users do not
> use their .data field at all. Each instance is removed here.
>
> Cc:
From: Johannes Berg
Date: Mon, 9 Oct 2017 09:40:12 +0200
> The QCA folks found another netlink problem - we were missing validation
> of some attributes. It's not super problematic since one can only read a
> few bytes beyond the message (and that memory must exist),
From: Herbert Xu
Date: Thu, 5 Oct 2017 11:40:54 +0800
> On Tue, Oct 03, 2017 at 07:45:06PM -0300, Marcelo Ricardo Leitner wrote:
>>
>> > Usually if you're invoking setkey from a non-sleeping code-path
>> > you're probably doing something wrong.
>>
>> Usually but not
From: Kees Cook
Date: Wed, 4 Oct 2017 16:26:58 -0700
> This refactors the only users of init_timer_pinned() to use
> the new timer_setup() and from_timer(). Drops the definition of
> init_timer_pinned().
>
> Cc: Chris Metcalf
> Cc: Thomas Gleixner
From: Kees Cook
Date: Wed, 4 Oct 2017 16:26:59 -0700
> This refactors the only users of init_timer_deferrable() to use
> the new timer_setup() and from_timer(). Removes definition of
> init_timer_deferrable().
>
> Cc: Benjamin Herrenschmidt
>
From: Kees Cook
Date: Wed, 4 Oct 2017 16:27:04 -0700
> Drop the arguments from the macro and adjust all callers with the
> following script:
>
> perl -pi -e 's/DEFINE_TIMER\((.*), 0, 0\);/DEFINE_TIMER($1);/g;' \
> $(git grep DEFINE_TIMER | cut -d: -f1 | sort -u |
From: Kalle Valo
Date: Mon, 25 Sep 2017 11:55:22 +0300
> here a pull request to net for 4.14, more info in the signed tag below.
> Please let me know if there are any problems.
Pulled, thanks Kalle.
From: Arnd Bergmann
Date: Fri, 22 Sep 2017 23:29:19 +0200
> When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large
> stack frames in some functions. This goes unnoticed normally because
> CONFIG_FRAME_WARN is disabled with CONFIG_KASAN by default as of commit
From: Arnd Bergmann
Date: Fri, 22 Sep 2017 23:29:18 +0200
> Inlining these functions creates lots of stack variables that each take
> 64 bytes when KASAN is enabled, leading to this warning about potential
> stack overflow:
>
> drivers/net/ethernet/rocker/rocker_ofdpa.c: In
From: Johannes Berg
Date: Tue, 19 Sep 2017 09:20:47 +0200
> Here's a new set of two small changes to prevent null pointer
> dereferences on malformed netlink messages.
>
> Please pull and let me know if there's any problem.
Pulled, thank you.
From: Kalle Valo
Date: Fri, 08 Sep 2017 18:50:01 +0300
> few fixes to net tree for 4.14. Note that this pull request contains the
> iwlwifi fix Linus hopes to have by end of the merge window. Please let
> me know if there are any problems.
Pulled, thanks for following up
From: Johannes Berg
Date: Thu, 7 Sep 2017 09:09:38 +0200
> During my long absence some things have accumulated, but there wasn't
> actually all that much that could've gone into the last cycle, and a
> fix or two was taken care of by others.
>
> The most important
From: Linus Torvalds
Date: Wed, 6 Sep 2017 16:27:15 -0700
> This pull request completely breaks Intel wireless for me.
>
> This is my trusty old XPS 13 (9350), using Intel Wireless 8260 (rev 3a).
>
> That remains a very standard Intel machine with absolutely zero
If it isn't a bug fix and it isn't in patchwork right now, I don't
want to see it.
This time around inappropriate submissions will be silently marked
as "deferred" in patchwork and not even looked at by me.
Thanks.
From: Kalle Valo
Date: Fri, 01 Sep 2017 17:34:43 +0300
> here's a pull request to net-next for 4.14. If the merge window opens on
> Sunday I'm planning to have this as the last one.
>
> Please let me know if there are any problems.
Ok, pulled, thanks.
From: Pavel Machek
Date: Thu, 31 Aug 2017 21:59:33 +0200
> Do you plan to send another pull request to Linus, and can you take
> the patch, please?
Yes and yes.
From: Pavel Machek
Date: Thu, 31 Aug 2017 20:57:19 +0200
> Hi!
>
>> From: Pavel Machek
>> Date: Thu, 31 Aug 2017 16:47:43 +0200
>>
>> > Dave, Linus -- can you still take the patch?
>>
>> Pavel, please do not bypass maintainers like this.
>>
>> It's really rude,
From: Pavel Machek
Date: Thu, 31 Aug 2017 16:47:43 +0200
> Dave, Linus -- can you still take the patch?
Pavel, please do not bypass maintainers like this.
It's really rude, and if you do things like that instead of
trying to work properly with us, your relationship with
these
From: Kalle Valo
Date: Mon, 28 Aug 2017 12:22:34 +0300
> here's a pull request to net-next for 4.14. Because I pulled
> wireless-drivers (at least that's my suspicion) the diffstat was wrong
> again and I created it manually. I recall Linus somewhere saying that in
>
From: Kalle Valo
Date: Fri, 25 Aug 2017 16:37:57 +0300
> here's pull request to net tree for 4.13, more info in the signed
> tag below. Please let me know if there are any problems.
Pulled, thanks Kalle.
From: Arvind Yadav
Date: Wed, 23 Aug 2017 16:22:20 +0530
> genl_ops are not supposed to change at runtime. All functions
> working with genl_ops provided by work with
> const genl_ops. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
From: Dan Williams
Date: Wed, 16 Aug 2017 21:11:47 -0500
> You'll probably say "aim for the 75% case" or something like that,
> which is fine, but then you're depending on your 75% case to be (a)
> single AP, (b) never move (eg, only bond wifi + ethernet), (c) little
> radio
From: Dan Williams
Date: Wed, 16 Aug 2017 16:22:41 -0500
> My biggest suggestion is that perhaps bonding should grow hysteresis
> for link speeds. Since WiFi can change speed every packet, you probably
> don't want the bond characteristics changing every couple seconds just
> in
From: James Feeney
Date: Wed, 16 Aug 2017 14:44:27 -0600
> On 08/13/2017 11:42 AM, Andreas Born wrote:
>> On a side note I would recommend some of my own reading to you about
>> patch submission in general [1] and on netdev specifically [2].
>
> Mmm - [2] and [3], I suspect.
From: Kalle Valo
Date: Tue, 15 Aug 2017 14:30:34 +0300
> more fixes to net tree for 4.13. More info in the signed tag below,
> please let me know if there are any problems.
Pulled, thanks Kalle.
From: Kalle Valo
Date: Mon, 07 Aug 2017 17:55:40 +0300
> here's the first pull request to net-next for 4.14, more info in the
> signed tag below. This time there's a simple conflict in iwlwifi but
> you can fix it just like Stephen did:
>
>
From: Bhumika Goyal
Date: Wed, 2 Aug 2017 23:27:14 +0530
> Add const to bin_attribute structure as it is only passed to the
> functions sysfs_{remove/create}_bin_file. The corresponding
> arguments are of type const, so declare the structure to be const.
>
> Signed-off-by:
From: Kalle Valo
Date: Fri, 28 Jul 2017 14:05:59 +
> Kalle Valo writes:
>
>> Hi Dave,
>>
>> here's a pull request for net, more info the signed tag below. Please
>> let me know if there are any problems.
>>
>> Kalle
>>
>> The following changes
From: Kalle Valo
Date: Fri, 21 Jul 2017 19:12:54 +0300
> important fixes for net which had accumulated while I was away. I only
> applied the brcmfmac and rtlwifi patches only eight hours ago and I
> haven't seen the kbuild report yet so they might have some build
>
From: "Gustavo A. R. Silva"
Date: Tue, 18 Jul 2017 15:37:11 -0500
> Remove unnecessary static on local function pointer _writer_.
> Such pointer is initialized before being used, on every
> execution path throughout the function. The static has no
> benefit and, removing
From: "Gustavo A. R. Silva"
Date: Tue, 18 Jul 2017 15:41:06 -0500
> Remove useless local variables last_read_point and last_txw_point and
> the code related.
>
> Signed-off-by: Gustavo A. R. Silva
Applied.
Tell your friends.
http://vger.kernel.org/~davem/net-next.html
From: Arend van Spriel
Date: Wed, 12 Jul 2017 13:49:23 +0200
> On 7/7/2017 10:09 PM, Arend van Spriel wrote:
>> The lower level nl80211 code in cfg80211 ensures that "len" is between
>> 25 and NL80211_ATTR_FRAME (2304). We subtract DOT11_MGMT_HDR_LEN (24)
>> from
It has gotten to the point that even casually walking around
Faro, Portugal last week, random German tourists would stop
me in the street and ask if net-next was open or not.
Therefore, in order to avoid any and all confusion I have created this
web site:
From: Johannes Berg
Date: Fri, 7 Jul 2017 11:29:01 +0200
> Just got a set of fixes in from Jouni/QCA, all netlink validation
> fixes. I assume they ran some kind of checker, but I don't know
> what kind :)
>
> Please pull and let me know if there's any problem.
From: Kalle Valo
Date: Mon, 03 Jul 2017 14:39:07 +0300
> here's the late pull request to net-next I mentioned about last week to
> get some new iwlwifi hw support to 4.13.
>
> If this is too late just drop the request and let me know, I can then
> resend it for 4.14 after
From: Samuel Ortiz
Date: Fri, 30 Jun 2017 11:37:20 +0200
> This is the NFC pull request for 4.13. We have:
>
> - A conversion to unified device and GPIO APIs for the
> fdp, pn544, and st{21,-nci} drivers.
> - A fix for NFC device IDs allocation.
> - A fix for the
From: Kalle Valo
Date: Fri, 30 Jun 2017 09:19:37 +0300
> here's a pull request to net-next for 4.13. Actually not really that big
> this time, more info in the signed tag below. Please let me know if you
> have any problems.
>
> Intel has new hardware coming up and they
1 - 100 of 394 matches
Mail list logo