public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Ashwin Ganti <ashwin.ganti@gmail.com>
Subject: Re: Staging tree status for the .33 kernel merge
Date: Mon, 4 Jan 2010 07:31:15 -0800	[thread overview]
Message-ID: <20100104153115.GB9435@kroah.com> (raw)
In-Reply-To: <20100104065755.GA26627@hallyn.com>

On Mon, Jan 04, 2010 at 12:57:55AM -0600, Serge E. Hallyn wrote:
> Quoting Greg KH (greg@kroah.com):
> ...
> > This means, unless someone steps up and starts doing real work (not
> > trivial spelling fixes) on the following drivers, they will be removed
> > in the future kernel releases.
> > 
> >  - arlan, netwave, strip, wavelan - wireless drivers mentioned above
> >    that are on the way out.  Slated for removal in 2.6.35
> >  - hv - Microsoft Hyper V drivers.  The developers again seem to have
> >    disappeared, this is getting old. Slated for removal in 2.6.35
> >  - p9auth - this will be removed in .34 unless someone steps up.
> 
> I think I've decided to try to push it.  I'm working with some patches
> at git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux-cr.git
> (branch p9auth.jan3.4 is latest).  I'll send patches as I feel they
> are ready - so far they pass testcases, but are too new for me to
> feel I should push them today.

Ok, send them on to me when you feel they are good enough.

thanks,

greg k-h

  reply	other threads:[~2010-01-04 15: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
2010-01-04  6:57 ` Serge E. Hallyn
2010-01-04 15:31   ` Greg KH [this message]
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=20100104153115.GB9435@kroah.com \
    --to=greg@kroah.com \
    --cc=ashwin.ganti@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge@hallyn.com \
    /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