Hi Jon,
On Mon, 27 Nov 2017 10:46:06 -0500 Jon Mason wrote:
>
> On Tue, Nov 21, 2017 at 5:19 PM, Stephen Rothwell
> wrote:
> >
> > On Mon, 20 Nov 2017 15:53:07 -0700 Logan Gunthorpe
> > wrote:
> >>
> >> On 20/11/17 03:37 PM, Stephen Rothwell wrote:
> >> > OK, all I need is the (git) URL f
On Tue, Nov 21, 2017 at 5:19 PM, Stephen Rothwell wrote:
> Hi Logan,
>
> On Mon, 20 Nov 2017 15:53:07 -0700 Logan Gunthorpe
> 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
On 21/11/17 03:19 PM, Stephen Rothwell wrote:
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.
No worries. There's no real rush on this but it should have been done
many cycles ago. After -r
Hi Logan,
On Mon, 20 Nov 2017 15:53:07 -0700 Logan Gunthorpe 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 d
On 11/20/2017 03:53 PM, Logan Gunthorpe 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
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 notice
Hi Dave,
On Mon, 20 Nov 2017 15:40:13 -0700 Dave Jiang wrote:
>
> He is still the NTB subsystem maintainer with more hardware drivers
> continue being added. I just removed him from the Intel hardware driver
> so he's not getting bothered with questions that should be coming to me.
Ah, my mistak
On 11/20/2017 03:37 PM, Stephen Rothwell wrote:
> Hi Logan,
>
> On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe
> 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?
>>
Hi Logan,
On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe 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
On 19/11/17 11:37 PM, Linus Torvalds wrote:
> Gaah. I guess I can take the pull request.
Many thanks.
> 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, b
On Sun, Nov 19, 2017 at 8:25 PM, Logan Gunthorpe wrote:
>
>
> On 19/11/17 11:12 AM, Linus Torvalds wrote:
>> I am now traveling, and am not inclined to pull stuff that hasn't been
>> in linux-next unless it's just obviously bug-fixes.
>
> Sigh. This work has been held up for two cycles due to issu
On 19/11/17 11:12 AM, Linus Torvalds wrote:
> I am now traveling, and am not inclined to pull stuff that hasn't been
> in linux-next unless it's just obviously bug-fixes.
Sigh. This work has been held up for two cycles due to issues with the
process.
If it's of any consideration, my Switchtec N
On Sun, Nov 19, 2017 at 5:25 AM, Jon Mason wrote:
> Hello Linus,
> Here is a new Switchtec NTB driver and a few NTB bug fixes for 4.15.
> It's been sitting in my ntb-next branch for some time and should be
> throughly tested. Please consider pulling them.
They may have been in your ntb-next bran
13 matches
Mail list logo
