Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: linux-next: Fixes tag needs some work in the crypto tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Herbert Xu <herbert@gondor.apana.org.au>,
        Linux Crypto List <linux-crypto@vger.kernel.org>
References: <20230724083703.5d995fb4@canb.auug.org.au>
CC:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
From:   Weili Qian <qianweili@huawei.com>
Message-ID: <8693972c-fa58-ba0f-9342-decb2f992215@huawei.com>
Date:   Mon, 24 Jul 2023 09:54:41 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20230724083703.5d995fb4@canb.auug.org.au>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Precedence: bulk

Sorry, my fault. I'll double check this in future submissions.
The correct tag is
Fixes: e3ac4d20e936 ("crypto: hisilicon/qm - enable PF and VFs communication")

@Herbert, Is there any way to modify it?

Regards,
Weili

On 2023/7/24 6:37, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   5cd4ed98cfb7 ("crypto: hisilicon/qm - flush all work before driver removed")
> 
> Fixes tag
> 
>   Fixes: ("crypto: hisilicon/qm - enable PF and VFs communication")
> 
> has these problem(s):
> 
>   - No SHA1 recognised
> 
> Maybe you meant
> 
> Fixes: e3ac4d20e936 ("crypto: hisilicon/qm - enable PF and VFs communication")
>