Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:43044 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753599AbdIDM6U (ORCPT ); Mon, 4 Sep 2017 08:58:20 -0400 From: Kalle Valo To: Stanislaw Gruszka Cc: Larry Finger , Helmut Schaa , linux-wireless , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: stable-kernel-rules: wireless and netdev-FAQ References: <20170831075514.GA12340@redhat.com> <26ef3184-a19e-1bb7-7aa4-4e8647210763@lwfinger.net> <20170901085738.GA18397@redhat.com> <87y3pymqw2.fsf@purkki.adurom.net> <20170902082223.GA11293@redhat.com> Date: Mon, 04 Sep 2017 15:58:15 +0300 In-Reply-To: <20170902082223.GA11293@redhat.com> (Stanislaw Gruszka's message of "Sat, 2 Sep 2017 10:22:24 +0200") Message-ID: <87ziaaoc2g.fsf_-_@kamboji.qca.qualcomm.com> (sfid-20170904_145848_456759_284465B1) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-wireless-owner@vger.kernel.org List-ID: (adding netdev and lkml) Stanislaw Gruszka writes: > On Fri, Sep 01, 2017 at 05:31:57PM +0300, Kalle Valo wrote: >> Stanislaw Gruszka 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