linux-kernel - Re: [GIT PULL] NTB bug fixes for v4.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171121093719.211f8194@canb.auug.org.au>
Date:   Tue, 21 Nov 2017 09:37:19 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Logan Gunthorpe <logang@...tatee.com>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Jon Mason <jdmason@...zu.us>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-ntb@...glegroups.com
Subject: Re: [GIT PULL] NTB bug fixes for v4.15

Hi Logan,

On Sun, 19 Nov 2017 23:51:48 -0700 Logan Gunthorpe <logang@...tatee.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