public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Cc: stable@kernel.org
Subject: -stable queues flushed out, missing anything?
Date: Wed, 30 Jul 2008 17:05:02 -0700	[thread overview]
Message-ID: <20080731000501.GA13477@kroah.com> (raw)

Hi all,

With the review cycles of 2.6.25 and 2.6.26 -stable kernels underway
right now, this is just a short note saying that all of the patches that
I have in the -stable queues have been included in these releases.

So, if I've missed anything that people have sent in the past that they
felt should be included in the .26 or .25 -stable kernel trees, please
resend them to the stable@kernel.org address (git commit id describing
the patch that is currently in Linus's tree is a requirement.)

And as always, the easiest way to get patches into the -stable tree is
to just add a simple:
	Cc: stable <stable@kernel.org>
to the Signed-off-by: area in a patch.  When it goes into Linus's tree,
the -stable team will be automatically notified of this and the patch
will then be merged into our trees as well.

thanks,

greg "finally flushed that mbox out" k-h

                 reply	other threads:[~2008-07-31  0:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080731000501.GA13477@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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