linux-kernel - Re: linux-next: manual merge of the jc

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: <20170703121332.2f0d43b5@lwn.net>
Date:   Mon, 3 Jul 2017 12:13:32 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Kamil Rytarowski <n54@....com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the jc_docs tree with the kbuild
 tree

On Mon, 3 Jul 2017 18:43:32 +0200
Kamil Rytarowski <n54@....com> wrote:

> Am I expected to do it myself and resend a new patch?
> 
No, there should be no need for that.  I've already mentioned the issue
in my pull request; if the same happens on the kbuild side, Linus will
not have a hard time figuring out what to do.

jon