linux-kernel - Re: linux-next: Fixes tag needs some work in the crypto tree

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: <20191118191223.1b7c11a9@canb.auug.org.au>
Date:   Mon, 18 Nov 2019 19:12:23 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Pascal Van Leeuwen <pvanleeuwen@...imatrix.com>
Cc:     Herbert Xu <herbert@...dor.apana.org.au>,
        Linux Crypto List <linux-crypto@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the crypto tree

Hi Pascal,

On Mon, 18 Nov 2019 07:58:42 +0000 Pascal Van Leeuwen <pvanleeuwen@...imatrix.com> wrote:
>
> My bad, I didn't know the Fixes tag should not be broken over
> lines (and that rather conflicted with the 75 characters per
> line rule here, which is why I did break it up).
> 
> I'm willing to fix that - except that I don't know how to create
> a patch that _only_ fixes the commit description of something 
> already pulled into the cryptodev tree?

Unless Herbert wants to rebase the crypto tree (and I think this is not
a good reason to do that), you should just consider this a learning
experience. :-)

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped