[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181108091251.GL9761@hirez.programming.kicks-ass.net>
Date: Thu, 8 Nov 2018 10:12:51 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>, x86@...nel.org,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
John Stultz <john.stultz@...aro.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Jonathan Corbet <corbet@....net>,
Andy Lutomirski <luto@...nel.org>,
Marc Zyngier <marc.zyngier@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Will Deacon <will.deacon@....com>,
Mark Brown <broonie@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [patch 2/2] Documentation/process: Add tip tree handbook
On Thu, Nov 08, 2018 at 08:40:12AM +0100, Ingo Molnar wrote:
> > + - Cc: ``cc-ed-person <person@...l>``
> > +
> > + If the patch should be backported to stable, then please add a '``Cc:
> > + stable@...r.kernel.org``' tag, but do not Cc stable when sending your
> > + mail.
>
> Can I suggest a more canonical form:
>
> Cc: <stable@...r.kernel.org> # v4.18 and later kernels
>
> It would be nice if people adding Cc: stable lines would actually try to
> figure out which exact kernel versions are affected.
I think Greg actually prefers we use stable@...nel.org, which is a
/dev/null target. His bot will then pick up on the tag once it hits
Linus' tree.
Powered by blists - more mailing lists