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
| ||
|
Date: Mon, 04 Sep 2017 15:58:15 +0300 From: Kalle Valo <kvalo@...eaurora.org> To: Stanislaw Gruszka <sgruszka@...hat.com> Cc: Larry Finger <Larry.Finger@...inger.net>, Helmut Schaa <helmut.schaa@...glemail.com>, linux-wireless <linux-wireless@...r.kernel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: stable-kernel-rules: wireless and netdev-FAQ (adding netdev and lkml) Stanislaw Gruszka <sgruszka@...hat.com> writes: > On Fri, Sep 01, 2017 at 05:31:57PM +0300, Kalle Valo wrote: >> Stanislaw Gruszka <sgruszka@...hat.com> writes: >> >> > On Thu, Aug 31, 2017 at 10:33:28AM -0500, Larry Finger wrote: >> >> Should the patch to wireless-drivers be annotated with a Stable reference so >> >> that it is added to 4.12 and 4.13? >> > >> > According to Documentation/networking/netdev-FAQ.txt networking patches >> > should not be marked cc:stable, instead a decent commit log should >> > be written describing a bugfix. Which I believe it is done for >> > this patch. >> >> But that's for net and net-next trees, not for wireless trees. With >> wireless patches we use "Cc: stable@..." references. > > Oh, ok. I was confused by below part of > Documentation/process/stable-kernel-rules.rst > (because wireless drivers are located in drivers/net/) > > - If the patch covers files in net/ or drivers/net please follow netdev stable > submission guidelines as described in > Documentation/networking/netdev-FAQ.txt Yeah, that's confusing and should be clarified that wireless follows traditional stable process. IIRC bluetooth does the same so it's not just wireless. Any volunteers to fix it? :) -- Kalle Valo
Powered by blists - more mailing lists