All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 19 Apr 2022 11:41:05 +0100	[thread overview]
Message-ID: <Yl6Rwe1okkWqC6ou@silpixa00400314> (raw)
In-Reply-To: <20220419071722.6e47c542@canb.auug.org.au>

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

  reply	other threads:[~2022-04-19 10:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 21:17 linux-next: Fixes tag needs some work in the crypto tree Stephen Rothwell
2022-04-19 10:41 ` Giovanni Cabiddu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-02 21:03 Stephen Rothwell
2023-07-23 22:37 Stephen Rothwell
2023-07-24  1:54 ` Weili Qian
2022-09-18 22:12 Stephen Rothwell
2022-09-19  9:38 ` Cabiddu, Giovanni
2022-09-20  8:28   ` Herbert Xu
2021-07-18 22:13 Stephen Rothwell
2021-07-19  5:43 ` Stephan Mueller
2021-07-19  5:46   ` Herbert Xu
2021-04-11 22:28 Stephen Rothwell
2019-12-11 20:37 Stephen Rothwell
2019-11-15 23:19 Stephen Rothwell
2019-11-18  7:58 ` Pascal Van Leeuwen
2019-11-18  8:12   ` Stephen Rothwell
2019-11-18 13:04     ` Herbert Xu
2019-08-02  6:02 Stephen Rothwell
2019-04-22 21:30 Stephen Rothwell
2019-04-23  4:08 ` Herbert Xu
2019-04-15 21:23 Stephen Rothwell
2019-04-16  1:05 ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yl6Rwe1okkWqC6ou@silpixa00400314 \
    --to=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marco.chiappero@intel.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.