DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1AD0220671
MIME-Version: 1.0
References: <a99840d5-7d57-ec1f-1c70-37ffa6cfd31b@lwfinger.net>
 <20181023143856.GD6850@thunk.org> <alpine.LRH.2.00.1810231833260.2860@gjva.wvxbf.pm>
 <20181023173747.GG6850@thunk.org>
In-Reply-To: <20181023173747.GG6850@thunk.org>
From:   Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date:   Tue, 23 Oct 2018 11:05:48 -0700
Message-ID: <CAKdAkRQvwe93nwLgEQuSsmbUbzMzVjO22wrfg=wzQtfHoSq2DA@mail.gmail.com>
Subject: Re: Is Fixes line enough?
To:     "Theodore Ts'o" <tytso@mit.edu>, Jiri Kosina <jikos@kernel.org>,
        Larry Finger <Larry.Finger@lwfinger.net>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        lkml <linux-kernel@vger.kernel.org>,
        linux-wireless <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Tue, Oct 23, 2018 at 10:38 AM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>
> On Tue, Oct 23, 2018 at 06:36:26PM +0200, Jiri Kosina wrote:
> > FWIW, I brought this up already at KS 2016, see Jon's coverage here:
> >
> >       https://lwn.net/Articles/705220/
> >
> > My primary motivation to bring that up back then was to try to reduce the
> > number of patches that are taken into -stable while there is no good
> > justification for that (by requiring each and every of those having Fixes:
> > present as a requirement), but it didn't really lead anywhere.
>
> Ah, I didn't get that you were trying to suggest that things only go
> into stable if it has both Fixes: *and* Cc: Stable.
>
> If that's the problem you were trying to solve, perhaps we could ask
> Stephen Rothwell if he would be willing to run a script that sends
> nag-o-grams to Maintainers who incluce patches in linux-next that have
> Cc: stable but neither Fixes nor a "# 4.x" appended to the end of the
> Cc: stable line?
>

Patches adding new PCI/USB/ACPI IDs or DMI quirks are usually accepted
into stable but normally lack "Fixes" tag.

Thanks.

-- 
Dmitry