linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Changes to gregkh's kernel trees
Date: Thu, 8 Oct 2009 11:41:50 -0700	[thread overview]
Message-ID: <20091008184150.GA20399@kroah.com> (raw)

Hi Stephen.

I've added a new tree to my kernel trees, the "staging.current" one.  It
works like the other "usb.current", "tty.current" and others in that it
contains patches from the staging tree that are going to be sent to
Linus for the "current" kernel release.

I've adjusted all of the NEXT_BASE tags in the series files to pull
from, and as always, it can all be found at:
	http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/

If you have any problems with this, please let me know.

thanks, and keep up the great work, it is much appreciated.

greg k-h

             reply	other threads:[~2009-10-08 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 18:41 Greg KH [this message]
2009-10-08 23:18 ` Changes to gregkh's kernel trees Stephen Rothwell

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=20091008184150.GA20399@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).