linux-kernel - Re: [GIT PULL] Squashfs pull request for 2.6.29

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090123003034.GA8141@suse.de>
Date:	Thu, 22 Jan 2009 16:30:34 -0800
From:	Greg KH <gregkh@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Dave Jones <davej@...hat.com>, mingo@...e.hu, geert@...ux-m68k.org,
	joern@...fs.org, lkml@...idb.org, kernel@...uxace.com,
	kay.sievers@...y.org, phillip@...gher.demon.co.uk,
	hch@...radead.org, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/