linux-kernel - Re: linux-next: Tree for June 19

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 20 Jun 2009 15:04:33 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	sfi-devel@...plefirmware.org
Subject: Re: linux-next: Tree for June 19

Hi Len,

On Sat, 20 Jun 2009 00:16:49 -0400 (EDT) Len Brown <lenb@...nel.org> wrote:
>
> Please add the Simple Firmware Interface "sfi-test" branch to linux-next:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-sfi-2.6.git sfi-test

Is this 2.6.31 or 32 material?

> A description of the project is on the SFI home page: http://simplefirmware.org/
> 
> Note: like ACPI's test branch, this branch will be occasionally re-based
> as the patches in it evolve.

That's fine.

Should I put just you as the contact, or add the mailing list as well?

What I tell everyone: all patches/commits in the tree/series must
have been:

	posted to a relevant mailing list
	reviewed
	unit tested
	destined for the next merge window (or the current release)

*before* they are included.  The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next 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
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped