linux-kernel - Re: Please add swiotlb.git 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]

Date:	Thu, 1 Nov 2012 08:34:03 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: Please add swiotlb.git tree to linux-next

Hi Konrad,

On Wed, 31 Oct 2012 08:59:29 -0400 Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
>
> Please add:
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git #linux-next
> 
> in the linux-next system. The branch is 'linux-next'. This would be the
> tree and branch used for maintaining the swiotlb and its different users.
> 
> The Ack's have already been given per this commit:
> 
> commit 6e28b761c5020c4bc943c7e38da86bea8af77d5c
> Author: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
> Date:   Mon Oct 8 16:28:05 2012 -0700
> 
>     MAINTAINERS: add Konrad as the SWIOTLB maintainer
>     
>     Now that I've an IA64 box on top of the other boxes (IBM with Calgary-X,
>     Intel VT-d, AMD Vi, and AMD GART - that can use SWIOTLB as fallback) I can
>     reliably do regression testing.
>     
>     Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
>     Cc: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
>     Cc: Ingo Molnar <mingo@...e.hu>
>     Acked-by: "H. Peter Anvin" <hpa@...or.com>
>     Cc: Thomas Gleixner <tglx@...utronix.de>
>     Acked-by: Tony Luck <tony.luck@...el.com>
>     Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
>     Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>

Added from today.

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