public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: devel@driverdev.osuosl.org, linux-usb@vger.kernel.org,
	linux-serial@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: USB, TTY, char/misc, and Staging trees now closed for 4.3
Date: Wed, 19 Aug 2015 07:52:23 -0700	[thread overview]
Message-ID: <20150819145223.GA20767@kroah.com> (raw)

Hi all,

Given that 4.2 will be out in a few days, it's time to close my trees
for new patches until 4.3-rc1 is out.

Please feel free to send me patches for these trees, but note that I'll
be ignoring them until 4.3-rc1 is out, at which point in time I'll start
reviewing them again and applying them to the various places they
belong.

thanks,

greg k-h

             reply	other threads:[~2015-08-19 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 14:52 Greg KH [this message]
2015-08-19 16:09 ` USB, TTY, char/misc, and Staging trees now closed for 4.3 Albino B Neto

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=20150819145223.GA20767@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-usb@vger.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