From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jon Mason <jdmason@kudzu.us>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ntb@googlegroups.com
Subject: Re: [GIT PULL] NTB bug fixes for v4.15
Date: Tue, 21 Nov 2017 09:37:19 +1100 [thread overview]
Message-ID: <20171121093719.211f8194@canb.auug.org.au> (raw)
In-Reply-To: <338c8f27-369b-11c4-f764-b8f726038f35@deltatee.com>
Hi Logan,
On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe <logang@deltatee.com> wrote:
>
> > I do want to protest the timing and the lack of linux-next coverage.
> > If it has really been ready for months, why hasn't it been in
> > linux-next at all?
>
> Understood. I can't speak for Jon, but in the future if I have patches
> in the queue, I will definitely remind him to send it to Stephen for the
> linux-next tree. And I'll make sure it gets there ahead of the merge window.
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.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-11-20 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 15:25 Jon Mason
2017-11-19 18:12 ` Linus Torvalds
2017-11-20 6:25 ` Logan Gunthorpe
2017-11-20 6:37 ` Linus Torvalds
2017-11-20 6:51 ` Logan Gunthorpe
2017-11-20 22:37 ` Stephen Rothwell [this message]
2017-11-20 22:40 ` Dave Jiang
2017-11-20 22:47 ` Stephen Rothwell
2017-11-20 22:53 ` Logan Gunthorpe
2017-11-20 22:55 ` Dave Jiang
2017-11-21 22:19 ` Stephen Rothwell
2017-11-21 22:25 ` Logan Gunthorpe
2017-11-27 15:46 ` Jon Mason
2017-11-27 20:53 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171121093719.211f8194@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jdmason@kudzu.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=logang@deltatee.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®