lkml.org 
[lkml]   [2017]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [GIT PULL] NTB bug fixes for v4.15
Hi Jon,

On Mon, 27 Nov 2017 10:46:06 -0500 Jon Mason <jdmason@kudzu.us> wrote:
>
> On Tue, Nov 21, 2017 at 5:19 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Mon, 20 Nov 2017 15:53:07 -0700 Logan Gunthorpe <logang@deltatee.com> wrote:
> >>
> >> On 20/11/17 03:37 PM, Stephen Rothwell wrote:
> >> > OK, all I need is the (git) URL for a tree/branch (or tag) and a
> >> > contact (or more than one) to whom I can report conflicts and build
> >> > problems. I then fetch it every day (so all you have to do it add stuff
> >> > to that branch when it is ready).
> >> >
> >> > I noticed that one of the current set of commits removed Jon as a
> >> > MAINTAINER, so I am not sure what part he would play.
> >> >
> >>
> >> The branch you would want to automatically fetch is
> >>
> >> https://github.com/jonmason/ntb.git ntb-next
> >>
> >> Jon's probably the contact you want for merge conflicts (Jon Mason
> >> <jdmason@kudzu.us>) as he's the one who typically pushes to those
> >> branches and submits PRs to Linus. You could also add the mailing list:
> >> linux-ntb@googlegroups.com. Dave and Allen are also maintainers but I'll
> >> let them speak up if they want to be contacted for this.
> >
> > So, I really need Jon to request this inclusion (sorry). And I would
> > prefer to not add it until after -rc1 has been released i.e. next week
> > probably.
>
> Thank you for doing this. Please include this branch at your
> convenience, and email me (and the NTB mailing list if possible) with
> any merge conflicts.

No worries, 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

\
 
 \ /
  Last update: 2017-11-27 22:18    [W:0.031 / U:29.600 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site