From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Veronika Molnarova <vmolnaro@redhat.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 perf-current tree
Date: Mon, 2 Sep 2024 15:42:32 -0300 [thread overview]
Message-ID: <ZtYHGDaoJrwLgs--@x1> (raw)
In-Reply-To: <20240902081837.6def2734@canb.auug.org.au>
On Mon, Sep 02, 2024 at 08:18:37AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 387ad33e5410 ("perf test pmu: Set uninitialized PMU alias to null")
>
> Fixes tag
>
> Fixes: 3e0bf9 ("perf pmu: Restore full PMU name wildcard support")
In the perf-tools-next I have it as:
commit 37e2a19c98bf99747ca997be876dfc13f9165e0a
Author: Veronika Molnarova <vmolnaro@redhat.com>
Date: Thu Aug 8 12:37:49 2024 +0200
perf test pmu: Set uninitialized PMU alias to null
Commit 3e0bf9fde2984469 ("perf pmu: Restore full PMU name wildcard
support") adds a test case "PMU cmdline match" that covers PMU name
wildcard support provided by function perf_pmu__match().
<SNIP>
Fixes: 3e0bf9fde2984469 ("perf pmu: Restore full PMU name wildcard support")
Signed-off-by: Veronika Molnarova <vmolnaro@redhat.com>
Cc: James Clark <james.clark@linaro.org>
Cc: Michael Petlan <mpetlan@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Radostin Stoyanov <rstoyano@redhat.com>
Link: https://lore.kernel.org/r/20240808103749.9356-1-vmolnaro@redhat.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
As I have:
⬢[acme@toolbox perf-tools-next]$ git config core.abbrev
16
⬢[acme@toolbox perf-tools-next]$
And scripts to make sure we get enough resolution to avoid such problems
I just checked and yeah, on perf-tools/perf-tools it is:
Fixes: 3e0bf9 ("perf pmu: Restore full PMU name wildcard support")
Signed-off-by: Veronika Molnarova <vmolnaro@redhat.com>
Cc: james.clark@arm.com
Cc: mpetlan@redhat.com
Cc: rstoyano@redhat.com
Link: https://lore.kernel.org/r/20240808103749.9356-1-vmolnaro@redhat.com
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
So I suggest Namhyung fixes up the Fixes tag to have a longer prefix for
the sha and Veronica to run:
⬢[acme@toolbox perf-tools]$ git config core.abbrev 16
⬢[acme@toolbox perf-tools]$ git config core.abbrev
16
⬢[acme@toolbox perf-tools]$
- Arnaldo
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Actually, the quoted SHA1 is too short and is ambiguous in my tree:
>
> $ git show 3e0bf9
> error: short object ID 3e0bf9 is ambiguous
> hint: The candidates are:
> hint: 3e0bf9fde298 commit 2024-06-26 - perf pmu: Restore full PMU name wildcard support
> hint: 3e0bf93e0354 tree
> fatal: ambiguous argument '3e0bf9': unknown revision or path not in the working tree.
>
> so you should use
>
> Fixes: 3e0bf9fde298 ("perf pmu: Restore full PMU name wildcard support")
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2024-09-02 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 22:18 linux-next: Fixes tag needs some work in the perf-current tree Stephen Rothwell
2024-09-02 18:42 ` Arnaldo Carvalho de Melo [this message]
2024-09-02 18:55 ` Namhyung Kim
2024-09-03 7:41 ` Veronika Molnarova
-- strict thread matches above, loose matches on Subject: below --
2021-09-27 21:35 Stephen Rothwell
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=ZtYHGDaoJrwLgs--@x1 \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vmolnaro@redhat.com \
/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.