From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Heads-up, last minutes changes in staging and tty trees.
Date: Tue, 10 Feb 2015 16:51:33 +0800 [thread overview]
Message-ID: <20150210085133.GA12902@kroah.com> (raw)
Hi Stephen,
I just realized that I hadn't pushed two of my trees into the branches
that you pull from until right now. So be prepared to see additional
staging and tty patches show up in the next linux-next. These are all
patches that are just basic cleanups / coding style stuff (staging
tree), or a new stand-alone serial driver (tty tree) and will be going
to Linus for the 3.20-rc1 merge window.
These have survived the 0-day bot just fine, so I feel comfortable with
a lack of build issues, but I'll wait a week just to be sure.
Sorry about this,
greg k-h
reply other threads:[~2015-02-10 8:51 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=20150210085133.GA12902@kroah.com \
--to=gregkh@linuxfoundation.org \
--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).