linux-kernel - Re: The Ambient Light Sensors for-next tree

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>] [day] [month] [year] [list]

Message-Id: <20100125103357.076abef7.sfr@canb.auug.org.au>
Date:	Mon, 25 Jan 2010 10:33:57 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	Zhang Rui <rui.zhang@...el.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	Greg KH <greg@...ah.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: The Ambient Light Sensors for-next tree

Hi Jonathan,

On Fri, 22 Jan 2010 15:25:38 +0000 Jonathan Cameron <jic23@....ac.uk> wrote:
>
> The ambient light sensors (ALS) patches have been on lkml for a while and
> the core has now been thoroughly reviewed.  The actual drivers
> will follow shortly as most are moves from elsewhere in the kernel tree.
> 
> Zhang Rui <rui.zhang@...el.com> is acting as the principle maintainer,
> whilst I'm handling the git tree and assisting with the more
> embedded devices.
> 
> To that end there is a git tree at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jic23/als.git for-next
> 
> and we were wondering if you could add this tree to linux-next?
> I've verified it applies cleanly on top of the current linux-next tree
> so it should merge fine *crosses fingers*

I have added the als tree to linux-next from today with you and Zhang Rui
listed as contacts for any problems.  I have cc'd this email to the more
general community so that people are aware of its inclusion.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgment of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
	Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@...b.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

Content of type "application/pgp-signature" skipped