All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.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 tree
Date: Wed, 2 Jul 2025 18:58:24 -0700	[thread overview]
Message-ID: <aGXjwJaa-FQ1TnPl@google.com> (raw)
In-Reply-To: <20250703080035.52470f9c@canb.auug.org.au>

Hello,

On Thu, Jul 03, 2025 at 08:00:35AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   7063002abb0c ("perf tools: Fix use-after-free in help_unknown_cmd()")
> 
> Fixes tag
> 
>   Fixes: 657a3efee43a ("libsubcmd: Avoid SEGV/use-after-free when commands aren't excluded")
> 
> has these problem(s):
> 
>   - Subject does not match target commit subject
>     Just use
>         git log -1 --format='Fixes: %h ("%s")'
> 
> maybe you meant
> 
> Fixes: 657a3efee43a ("lib subcmd: Avoid memory leak in exclude_cmds")
> 
> or
> 
> Fixes: 4b96679170c6 ("libsubcmd: Avoid SEGV/use-after-free when commands aren't excluded")

Sorry for the trouble, it should be the latter.  Will fix and update.

Thanks,
Namhyung


  reply	other threads:[~2025-07-03  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 22:00 linux-next: Fixes tag needs some work in the perf tree Stephen Rothwell
2025-07-03  1:58 ` Namhyung Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-17 22:47 Stephen Rothwell
2022-12-13 21:31 Stephen Rothwell
2022-12-13 21:35 ` Arnaldo Carvalho de Melo
2022-11-24 20:57 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=aGXjwJaa-FQ1TnPl@google.com \
    --to=namhyung@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.