linux-ext4 - Re: dax-misc branch for 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: <20160518133422.6dfbad0b@canb.auug.org.au>
Date:	Wed, 18 May 2016 13:34:22 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	"Verma, Vishal L" <vishal.l.verma@...el.com>
Cc:	"Williams, Dan J" <dan.j.williams@...el.com>, <hch@...radead.org>,
	<jack@...e.cz>, <linux-nvdimm@...ts.01.org>, <tytso@....edu>,
	<linux-fsdevel@...r.kernel.org>, <linux-ext4@...r.kernel.org>
Subject: Re: dax-misc branch for linux-next

Hi Vishal,

On Tue, 17 May 2016 18:36:47 +0000 "Verma, Vishal L" <vishal.l.verma@...el.com> wrote:
>
> I understand this is a bit out of the norm, but:
> 
> Could you please merge
> 
> 	https://git.kernel.org/cgit/linux/kernel/git/nvdimm/nvdimm.git dax-misc
> 
> into linux-next for some coverage.
> 
> It is a bit late to the ready-before-merge-window deadline, due to
> having to coordinate dependencies between trees/patchsets. I'm hoping to
> send a pull request for this later in the merge window (once ext4 is
> merged).

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement 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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html