dax-misc branch for linux-next

dax-misc branch for linux-next

[Verma, Vishal L]

Hi Stephen,

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).


Thanks,
	-Vishal
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

dax-misc branch for linux-next

[Verma, Vishal L]

Hi Stephen,

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).


Thanks,
	-Vishal

Re: dax-misc branch for linux-next

[Stephen Rothwell]

Hi Vishal,

On Tue, 17 May 2016 18:36:47 +0000 "Verma, Vishal L" <vishal.l.verma@intel.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@canb.auug.org.au

Re: dax-misc branch for linux-next

[Stephen Rothwell]

Hi Vishal,

On Tue, 17 May 2016 18:36:47 +0000 "Verma, Vishal L" <vishal.l.verma@intel.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@canb.auug.org.au

Re: dax-misc branch for linux-next

[Stephen Rothwell]

Hi Vishal,

On Tue, 17 May 2016 18:36:47 +0000 "Verma, Vishal L" <vishal.l.verma@intel.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@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: dax-misc branch for linux-next

[Vishal Verma]

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

On Tue, May 17, 2016 at 9:34 PM, Stephen Rothwell <sfr@canb.auug.org.au>
wrote:

> Hi Vishal,
>
> On Tue, 17 May 2016 18:36:47 +0000 "Verma, Vishal L" <
> vishal.l.verma@intel.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.
>

Thanks for merging, Stephen, and also for resolving the conflicts. I meant
to post a branch with the example resolution for the nvdimm tree, but
somehow it completely slipped my mind.

[-- Attachment #2: Type: text/html, Size: 2418 bytes --]