linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Elaboration on "Equivalent fix must already exist in Linus' tree"
Date: Mon, 2 Mar 2009 22:27:21 -0800	[thread overview]
Message-ID: <20090303062721.GA4091@kroah.com> (raw)
In-Reply-To: <43e72e890903022143k83890afr6673753f52c5ff8@mail.gmail.com>

On Mon, Mar 02, 2009 at 09:43:26PM -0800, Luis R. Rodriguez wrote:
> While extending the documentation for submitting Linux wireless bug
> reports [1] we note the stable series policy on patches -- that of
> having an equivalent fix already in Linus' tree. I find this
> documented in Documentation/stable_kernel_rules.txt but I'm curious if
> there is any other resource which documents this or elaborates on this
> a bit more.

Simple is better, do you really want a longer version of that same file?

Is there something confusing in it?

And as always, a simple:
	Cc: stable <stable@kernel.org>
in the patch itself is the easiest way to get it automatically included
in the next -stable releases after it hits Linus's tree.

What more do people want?  Personal invitations?

Is it time to break out the caligraphy pens and wax seals?

thanks,

greg k-h

  parent reply	other threads:[~2009-03-03  6:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03  5:43 Elaboration on "Equivalent fix must already exist in Linus' tree" Luis R. Rodriguez
2009-03-03  5:57 ` Jeff Garzik
2009-03-03  6:44   ` Luis R. Rodriguez
2009-03-03  7:20     ` Jeff Garzik
2009-03-03  7:26     ` Greg KH
2009-03-03  7:37       ` Luis R. Rodriguez
2009-03-03  7:42         ` david
2009-03-03  7:57           ` Luis R. Rodriguez
2009-03-03  9:16             ` Theodore Tso
2009-03-03 15:19             ` Stefan Richter
2009-03-03 14:53         ` Greg KH
2009-03-03 15:27         ` Stefan Richter
2009-03-03 17:23           ` Luis R. Rodriguez
2009-03-03 18:13             ` Stefan Richter
2009-03-03 18:43               ` Luis R. Rodriguez
2009-03-03 22:55                 ` david
2009-03-03  6:27 ` Greg KH [this message]
2009-03-03 14:43   ` John W. Linville

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=20090303062721.GA4091@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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).