From: Namhyung Kim <namhyung@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Fixes tags need work in the perf tree
Date: Wed, 15 Apr 2026 22:54:19 -0700 [thread overview]
Message-ID: <aeB5i8Zr2U6of_3I@google.com> (raw)
In-Reply-To: <ad9kc24cz9mhPXWJ@sirena.org.uk>
Hello,
On Wed, Apr 15, 2026 at 11:12:03AM +0100, Mark Brown wrote:
> In commit
>
> 841dbf4871c57 ("perf loongarch: Fix build failure with CONFIG_LIBDW_DWARF_UNWIND")
>
> Fixes tag
>
> Fixes: e62fae9d9e8 ("perf unwind-libdw: Fix a cross-arch unwinding bug")
>
> 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").
Sorry for the trouble. I already have the config in my git config but I
missed to check it in contributors' patch. I'll update my b4 script -
I hope checkpatch would catch this kind of problem next time.
Thanks,
Namhyung
prev parent reply other threads:[~2026-04-16 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 10:12 Fixes tags need work in the perf tree Mark Brown
2026-04-16 5:54 ` Namhyung Kim [this message]
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=aeB5i8Zr2U6of_3I@google.com \
--to=namhyung@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox