netdev - Re: pull-request: ieee802154 2018-05-08

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180508.200638.1908252284342544792.davem@davemloft.net>
Date:   Tue, 08 May 2018 20:06:38 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     stefan@....samsung.com
Cc:     s.schmidt@...sung.com, linux-wpan@...r.kernel.org,
        alex.aring@...il.com, netdev@...r.kernel.org
Subject: Re: pull-request: ieee802154 2018-05-08

From: Stefan Schmidt <stefan@....samsung.com>
Date: Tue, 8 May 2018 21:55:37 +0200

> On 05/08/2018 04:18 PM, David Miller wrote:
>> Please submit the -stable fix directly, you can feel free to CC: me.
> 
> Will do when the patch hits Linus git tree.
> 
> I have a quick question on the process here. From the netdev-faq document
> I was under the impression all stable patches under net/ and drivers/net
> should be brought up to you and would be handled by you.
> 
> Does this apply to the core part of net (I fully understand that ieee802154
> is rather a niche) or is there some other reason for this exception?
> 
> Both processes (the normal stable one as well as the slightly different one
> for net/) would be fine to go with for me. Just need to know which one I
> should use for future stable patches. :-)
> 
> regards
> Stefan Schmidt

Generally wireless and ipsec have been submitting them directly,
sometimes the Intel ethernet guys do too.

Sometimes this makes things easier for me, and I'll ask you to submit
things directly when that is the case like right now.

Thank you.