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;
Date:   Tue, 19 Apr 2022 11:41:05 +0100
From:   Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Herbert Xu <herbert@gondor.apana.org.au>
Cc:     Linux Crypto List <linux-crypto@vger.kernel.org>,
        Marco Chiappero <marco.chiappero@intel.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the crypto tree
Message-ID: <Yl6Rwe1okkWqC6ou@silpixa00400314>
References: <20220419071722.6e47c542@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220419071722.6e47c542@canb.auug.org.au>
Organization: Intel Research and Development Ireland Ltd - Co. Reg. #308263 -
 Collinstown Industrial Park, Leixlip, County Kildare - Ireland
Precedence: bulk

Thanks Stephen.

On Tue, Apr 19, 2022 at 07:17:22AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   c690c7f6312c ("crypto: qat - rework the VF2PF interrupt handling logic")
> 
> Fixes tag
> 
>   Fixes: 993161d ("crypto: qat - fix handling of VF to PF interrupts")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future by setting core.abbrev to 12 (or
>     more) or (for git v2.11 or later) just making sure it is not set
>     (or set to "auto").
Apologies, I missed this during the review of the patch.

@Herbert, should I resend the patch with the correct Fixes tag or can
you amend the commit in your tree.

This should be the correct tag:
    Fixes: 993161d36ab5 ("crypto: qat - fix handling of VF to PF interrupts")

Regards,

-- 
Giovanni