public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-usb@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.35 merge window is over for USB
Date: Fri, 21 May 2010 08:21:41 -0700	[thread overview]
Message-ID: <20100521152141.GA18603@kroah.com> (raw)

Hi all,

If you haven't noticed, all of the new features for USB are now merged
in Linus's tree for the .35 kernel version.  At this point in time, I'm
only expecting there to be minor bugfixes and new device ids for the .35
kernel for the USB subsystem.  Anything else, will be gladly accepted by
me at any time, but note that I will be queueing it up for the .36
kernel release.

If anyone has any questions, please let me know.

thanks,

greg k-h

p.s. Yes, this is in direct response to the crazy direct emails that
people love to send me begging me to take their untested and buggy code
with the promise of them fixing it up later at some future time.  AMD,
this means you.

             reply	other threads:[~2010-05-21 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 15:21 Greg KH [this message]
2010-05-21 20:26 ` 2.6.35 merge window is over for USB Sergei Shtylyov
2010-05-21 20:37   ` Greg KH

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=20100521152141.GA18603@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@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