From: Greg KH <greg@kroah.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: Staging tree status for the .33 kernel merge
Date: Wed, 23 Dec 2009 08:33:31 -0800 [thread overview]
Message-ID: <20091223163331.GB26904@kroah.com> (raw)
In-Reply-To: <20091223105315.GA27229@Chamillionaire.breakpoint.cc>
On Wed, Dec 23, 2009 at 11:53:15AM +0100, Sebastian Andrzej Siewior wrote:
> * Greg KH | 2009-12-22 16:54:47 [-0800]:
>
> >Here's a summary of the state of the drivers/staging/ tree, basically
> >what will be coming in the 2.6.33 merge, and what the status of the
> >different drivers are so far.
>
> I can't find usbip in your summary. Is there nothing to say or did you
> just forgot about it?
Oops, I forgot about it. It's slated to be removed in .35 as well,
because no one is working on it.
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-23 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 0:54 Staging tree status for the .33 kernel merge Greg KH
2009-12-23 10:53 ` Sebastian Andrzej Siewior
2009-12-23 16:33 ` Greg KH [this message]
2010-01-04 6:57 ` Serge E. Hallyn
2010-01-04 15:31 ` Greg KH
2010-01-04 17:16 ` Ashwin Ganti
2010-01-04 17:38 ` Serge E. Hallyn
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=20091223163331.GB26904@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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