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: <CA+55aFwmGk=279M9D2XzpuVoMuB_MPw+2n4vb47ZYh72GM6gaw@mail.gmail.com>
Date:   Sun, 19 Nov 2017 20:37:46 -1000
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Logan Gunthorpe <logang@...tatee.com>
Cc:     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

On Sun, Nov 19, 2017 at 8:25 PM, Logan Gunthorpe <logang@...tatee.com> 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 issues with the
> process.
>
> If it's of any consideration, my Switchtec NTB patches were in one of my
> repos which is subscribed to the kbuild test robot. I did receive a
> build success notification email on it a few months ago. It's also an
> isolated driver which shouldn't have any effect on any other systems.

Gaah. I guess I can take the pull request.

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?

         Linus