Re: [PULL REQUEST] nfsd changes for 4.15

[Stephen Rothwell <sfr@canb.auug.org.au>]

Hi Anna,

On Thu, 30 Nov 2017 15:53:22 -0500 Anna Schumaker <Anna.Schumaker@Netapp.com> wrote:
>
> On 11/30/2017 03:47 PM, Stephen Rothwell wrote:
> > 
> > On Thu, 30 Nov 2017 15:24:59 -0500 Anna Schumaker <Anna.Schumaker@Netapp.com> wrote:  
> >>
> >> What are the steps for adding my tree to next?  
> > 
> > I just need a (git) url for the tree and branch (or tag) that you will
> > update when stuff is ready to be in linux-next.  I will fetch that
> > branch every morning, so once set up I automatically get updates.  
> 
> Let's go with the "linux-next" branch at git://git.linux-nfs.org/projects/anna/linux-nfs.git
> 
> > 
> > Also, a list of contacts that I can report problems (conflicts, build
> > failures/warnings etc) to (probably yourself, but maybe a mailing list
> > and any others who can fix problems.
> >   
> 
> Let's go with me (anna.schumaker@netapp.com), Trond (trondmy@primarydata.com), and linux-nfs@vger.kernel.org.

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