From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dave Jones <davej@redhat.com>,
mingo@elte.hu, geert@linux-m68k.org, joern@logfs.org,
lkml@davidb.org, kernel@linuxace.com, kay.sievers@vrfy.org,
phillip@lougher.demon.co.uk, hch@infradead.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29
Date: Thu, 22 Jan 2009 16:30:34 -0800 [thread overview]
Message-ID: <20090123003034.GA8141@suse.de> (raw)
In-Reply-To: <20090122161659.53de9e56.akpm@linux-foundation.org>
On Thu, Jan 22, 2009 at 04:16:59PM -0800, Andrew Morton wrote:
> My question is: what is the process for moving things out of staging/ and
> into the kernel proper? We don't want to be merging ex-crap code which has
> had its whitespace and wrappers cleaned up by a person who is not suitably
> experienced in the relevant subsystem.
>
> It _should_ (I think) be "OK, this is ready for us to start reviewing".
> ie: treat it as if it had just come in from a random new submitter.
I agree, and I will do just that.
> a) If that happens, who will be responding to the review comments? Who
> was the submitter?
For drivers that don't have an active developer, I'll handle the review
commends and fix things up. Some of these drivers do have active
developers, and I'm sure they will be the ones handling the review as
well.
> b) What happens if it is then decided that we just don't want that code
> in the tree at all?
As it's "just a driver", the odds of that happening are probably going
to be very slim. We can cross that bridge when we come to it.
> c) Has any code yet made the transition out of staging and into the
> kernel proper? If so, which?
Not yet, but some of the network drivers are looking much better and I
think they will move out soon.
One of the v4l drivers should move out for .30, I need to get some time
to send the patch to those developers.
thanks,
greg k-h
next prev parent reply other threads:[~2009-01-23 0:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 16:48 [GIT PULL] Squashfs pull request for 2.6.29 Phillip Lougher
2009-01-08 16:50 ` Christoph Hellwig
2009-01-08 17:05 ` Phillip Lougher
2009-01-08 17:11 ` Geert Uytterhoeven
2009-01-08 23:55 ` H. Peter Anvin
2009-01-09 1:53 ` Andrew Morton
2009-01-09 2:11 ` Phillip Lougher
2009-01-09 2:24 ` Kay Sievers
2009-01-09 2:36 ` Phil Oester
2009-01-09 16:54 ` Jörn Engel
2009-01-09 19:37 ` David Brown
2009-01-09 21:19 ` Jörn Engel
2009-01-10 12:43 ` Ingo Molnar
2009-01-10 16:50 ` Jörn Engel
2009-01-10 18:12 ` Andrew Morton
2009-01-10 18:30 ` Linus Torvalds
2009-01-10 19:57 ` Jeff Garzik
2009-01-10 20:16 ` Leon Woestenberg
2009-01-11 6:36 ` Valdis.Kletnieks
2009-01-10 19:19 ` Olivier Galibert
2009-01-10 22:15 ` Ingo Molnar
2009-01-11 9:30 ` Geert Uytterhoeven
2009-01-11 15:39 ` Ingo Molnar
2009-01-11 16:30 ` Greg KH
2009-01-22 21:50 ` Dave Jones
2009-01-22 21:57 ` Randy Dunlap
2009-01-22 22:15 ` Greg KH
2009-01-22 21:58 ` Greg KH
2009-01-22 22:26 ` Ingo Molnar
2009-01-22 22:50 ` Kyle McMartin
2009-01-22 23:04 ` Greg KH
2009-01-22 23:25 ` Evgeniy Polyakov
2009-01-22 23:34 ` Kyle McMartin
2009-01-22 23:41 ` Ingo Molnar
2009-01-22 23:28 ` Evgeniy Polyakov
2009-01-22 22:16 ` Ingo Molnar
2009-01-22 22:24 ` Pekka Enberg
2009-01-23 0:16 ` Andrew Morton
2009-01-23 0:30 ` Greg KH [this message]
2009-01-09 2:30 ` Harvey Harrison
2009-01-09 11:25 ` KOSAKI Motohiro
2009-01-09 12:02 ` Alan Cox
2009-01-09 21:56 ` Linus Torvalds
2009-01-09 22:08 ` Andrew Morton
2009-01-09 22:12 ` Linus Torvalds
2009-01-09 22:26 ` Alan Cox
2009-01-09 22:36 ` Harvey Harrison
2009-01-11 3:01 ` Phillip Lougher
2009-01-11 3:06 ` H. Peter Anvin
2009-01-09 16:32 ` Geert Uytterhoeven
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=20090123003034.GA8141@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=joern@logfs.org \
--cc=kay.sievers@vrfy.org \
--cc=kernel@linuxace.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@davidb.org \
--cc=mingo@elte.hu \
--cc=phillip@lougher.demon.co.uk \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).