linux-kernel - Re: linux-kbuild.git

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

Message-Id: <20091127152211.55043dbb.sfr@canb.auug.org.au>
Date:	Fri, 27 Nov 2009 15:22:11 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Michal Marek <mmarek@...e.cz>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	"Aníbal Monsalve Salazar" 
	<anibal@...ian.org>, Andrew Morton <akpm@...ux-foundation.org>,
	linux-kbuild@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: linux-kbuild.git

Hi Michal,

On Thu, 26 Nov 2009 20:37:50 +0100 Sam Ravnborg <sam@...nborg.org> wrote:
>
> On Thu, Nov 26, 2009 at 01:26:09PM +0100, Michal Marek wrote:
> > 
> > I went through the patches posted to linux-kbuild and picked those that
> > were easy enough to review, looked safe and worked for me. I also took
> > Sam's series from kbuild-next.git, but I didn't really review it yet, so
> > there is no signoff from me (TBD). The repo is at
> > 
> >   git://repo.or.cz/linux-kbuild.git for-next
> 
> Looks good.
> Good to see you picked up some of the patches that were pending.
> 
> Stephen - please replace my kbuild trees with this.

I have replaced this from today.  Do you intend to run the equivalent of
the kbuild-current tree (bug fixes for the current release while they are
waiting to go to Linus)?  I have removed the kbuild-current tree for now
since the only commit in it is in the new kbuild tree.

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