Adding my fscache-next branch to linux-next

Adding my fscache-next branch to linux-next

[David Howells]

Hi Stephen,

Could you add my fscache-next branch, which is in this repo:

	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git

to linux-next please?

Note that it might conflict with anything Trond and/or Anna ask you to pull
for NFS, in which case I'll drop the NFS patches from it and seek to get Trond
and Anna to take them into the NFS tree.

Thanks,
David

Re: Adding my fscache-next branch to linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

Hi David,

On Mon, 25 Jan 2021 21:53:10 +0000 David Howells <dhowells@redhat.com> wrote:
>
> Could you add my fscache-next branch, which is in this repo:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
> 
> to linux-next please?
> 
> Note that it might conflict with anything Trond and/or Anna ask you to pull
> for NFS, in which case I'll drop the NFS patches from it and seek to get Trond
> and Anna to take them into the NFS tree.

Added from tomorrow.

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@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]