From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Marc Zyngier <maz@kernel•org>
Cc: Wudi Wang <wangwudi@hisilicon•com>,
Shaokun Zhang <zhangshaokun@hisilicon•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 irqchip tree
Date: Fri, 17 Dec 2021 05:20:46 +1100 [thread overview]
Message-ID: <20211217052046.619006b8@canb.auug.org.au> (raw)
In-Reply-To: <20211217051927.68516ed4@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi all,
On Fri, 17 Dec 2021 05:19:27 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> In commit
>
> d094b4332232 ("irqchip/irq-gic-v3-its.c: Force synchronisation when issuing INVALL")
>
> Fixes tag
>
> Fixes: cc2d3216f53 ("irqchip: GICv3: ITS command queue")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> Can be fixed 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").
That commit is actually in the irqchip-fixes tree, sorry.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-12-16 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 18:19 linux-next: Fixes tag needs some work in the irqchip tree Stephen Rothwell
2021-12-16 18:20 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 13:06 Stephen Rothwell
2022-03-21 14:16 ` Marc Zyngier
2020-05-31 18:06 Stephen Rothwell
2020-05-31 19:49 ` Marc Zyngier
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=20211217052046.619006b8@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maz@kernel$(echo .)org \
--cc=wangwudi@hisilicon$(echo .)com \
--cc=zhangshaokun@hisilicon$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox