From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Paul McKenney <paulmck@linux.vnet.ibm.com>,
John Stultz <john.stultz@linaro.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Andy Lutomirski <luto@kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Will Deacon <will.deacon@arm.com>,
Mark Brown <broonie@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [patch 2/2] Documentation/process: Add tip tree handbook
Date: Thu, 8 Nov 2018 03:05:32 -0800 [thread overview]
Message-ID: <20181108110532.GA30851@kroah.com> (raw)
In-Reply-To: <20181108091251.GL9761@hirez.programming.kicks-ass.net>
On Thu, Nov 08, 2018 at 10:12:51AM +0100, Peter Zijlstra wrote:
> On Thu, Nov 08, 2018 at 08:40:12AM +0100, Ingo Molnar wrote:
> > > + - Cc: ``cc-ed-person <person@mail>``
> > > +
> > > + If the patch should be backported to stable, then please add a '``Cc:
> > > + stable@vger.kernel.org``' tag, but do not Cc stable when sending your
> > > + mail.
> >
> > Can I suggest a more canonical form:
> >
> > Cc: <stable@vger.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@kernel.org, which is a
> /dev/null target. His bot will then pick up on the tag once it hits
> Linus' tree.
I really do not care either way what address is used. Both work fine.
thanks,
greg k-h
next prev parent reply other threads:[~2018-11-08 11:05 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:10 [patch 0/2] Documentation/process: Add subsystem/tree handbook Thomas Gleixner
2018-11-07 17:10 ` [patch 1/2] Documentation/process: Add maintainer handbooks section Thomas Gleixner
2018-11-07 17:10 ` [patch 2/2] Documentation/process: Add tip tree handbook Thomas Gleixner
2018-11-07 17:44 ` Thomas Gleixner
2018-11-07 19:57 ` Paul E. McKenney
2018-11-07 19:38 ` Paul E. McKenney
2018-11-08 7:05 ` Ingo Molnar
2018-11-08 7:14 ` Ingo Molnar
2018-11-08 7:19 ` Ingo Molnar
2018-11-08 7:30 ` Ingo Molnar
2018-11-08 7:40 ` Ingo Molnar
2018-11-08 9:12 ` Peter Zijlstra
2018-11-08 11:05 ` Greg Kroah-Hartman [this message]
2018-11-08 17:19 ` Dan Williams
2018-11-08 17:24 ` Borislav Petkov
2018-11-08 17:40 ` Paul E. McKenney
2018-11-08 19:58 ` Thomas Gleixner
2018-11-08 20:05 ` Paul E. McKenney
2018-11-08 21:06 ` Greg KH
2018-11-08 21:08 ` Greg KH
2018-11-08 22:38 ` Thomas Gleixner
2018-11-08 20:14 ` Theodore Y. Ts'o
2018-11-08 20:22 ` Thomas Gleixner
2018-11-08 21:04 ` Greg KH
2018-11-08 22:19 ` Theodore Y. Ts'o
2018-11-08 22:33 ` Greg KH
2018-11-08 22:56 ` Dan Williams
2018-11-08 7:46 ` Ingo Molnar
2018-11-08 8:04 ` Ingo Molnar
2018-11-08 8:13 ` Ingo Molnar
2018-11-08 8:18 ` Ingo Molnar
2018-11-08 8:30 ` Ingo Molnar
2018-11-07 19:48 ` [patch 0/2] Documentation/process: Add subsystem/tree handbook Jonathan Corbet
2018-11-07 19:58 ` Dan Williams
2018-11-07 20:51 ` Thomas Gleixner
2018-11-08 14:49 ` Jonathan Corbet
2018-11-08 15:05 ` Peter Zijlstra
2018-11-08 15:19 ` Jonathan Corbet
2018-11-08 16:05 ` Paul E. McKenney
2018-11-08 16:21 ` Theodore Y. Ts'o
2018-11-08 16:32 ` Mark Brown
2018-11-08 17:32 ` Dan Williams
2018-11-13 23:15 ` Mark Brown
2018-11-08 16:33 ` Jonathan Corbet
2018-11-08 19:46 ` Theodore Y. Ts'o
2018-11-08 15:49 ` Thomas Gleixner
2020-12-17 15:05 ` Borislav Petkov
2020-12-17 17:53 ` Jonathan Corbet
2020-12-17 17:58 ` Borislav Petkov
2018-11-12 5:52 ` Ingo Molnar
2021-09-13 15:39 [PATCH 0/2] doc: Add tip maintainer's handbook Borislav Petkov
2021-09-13 15:39 ` [PATCH 2/2] Documentation/process: Add tip tree handbook Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181108110532.GA30851@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave.hansen@linux.intel.com \
--cc=frederic@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).