Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <6604f8be7a73f727cbfae7f93a74da706e46befc.camel@chronox.de>
Subject: Re: linux-next: Fixes tag needs some work in the crypto tree
From:   Stephan Mueller <smueller@chronox.de>
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Linux Crypto List <linux-crypto@vger.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Date:   Mon, 19 Jul 2021 07:43:29 +0200
In-Reply-To: <20210719081320.1d205c98@canb.auug.org.au>
References: <20210719081320.1d205c98@canb.auug.org.au>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Am Montag, dem 19.07.2021 um 08:13 +1000 schrieb Stephen Rothwell:
> Hi all,

Hi Stephen, Herbert
> 
> In commit
> 
>   5261cdf457ce ("crypto: drbg - select SHA512")
> 
> Fixes tag
> 
>   Fixes: 9b7b94683a9b "crypto: DRBG - switch to HMAC SHA512 DRBG as default
> 
> has these problem(s):
> 
>   - Subject has leading but no trailing quotes
> 
> Please do not split Fixes tags over more than one line.
> 

Thank you for the report.

Herbert, how do we go about this fix? I can surely prepare another patch. But
considering that the old patch is already in the git tree, are you considering
to revert it?

Thanks
Stephan