linux-kernel - Re: Please add an IPMI tree to linux-next

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: <20140911093514.5b40f0ec@canb.auug.org.au>
Date:	Thu, 11 Sep 2014 09:35:14 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Corey Minyard <cminyard@...sta.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Please add an IPMI tree to linux-next

Hi Corey,

On Wed, 10 Sep 2014 08:27:01 -0500 Corey Minyard <cminyard@...sta.com> wrote:
>
> Could you add:
> 
>    git://git.code.sf.net/p/openipmi/linux-ipmi for-next
> 
> to the linux-next tree?  This is bug fixes and minor enhancements for the
> IPMI driver.

Added from today with just you listed as the contact.

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

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)