From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Jianping Liu <frankjpliu@tencent.com>,
Ming Wang <wangming01@loongson.cn>
Subject: Re: Missing signoff in the perf tree
Date: Fri, 25 Sep 2026 00:48:10 +0200 [thread overview]
Message-ID: <arWoqiABqzp3Zn6x@x2> (raw)
In-Reply-To: <arWl_CVE0g8dSTSU@sirena.org.uk>
On Thu, Sep 24, 2026 at 11:36:44PM +0100, Mark Brown wrote:
> Commit
>
> 4c09f6c47b769 ("perf annotate: Fix NULL pointer dereference in loongarch_call__parse")
>
> is missing a Signed-off-by from its author
The patch had a --- before the author's s-o-b, so it got lost, I'll
adding it and will force push:
============================================================
the address-based symbol lookup so that ops->target.sym can still be
resolved via maps__find_ams() using the already-parsed target address.
This preserves is_call semantics and keeps TUI navigation working.
---
Changes from v1:
- Instead of returning -1 when the '<sym>' token is absent jump to the
address-based symbol lookup so that maps__find_ams() can still resolve
ops->target.sym from the already parsed target address.
- Link to v1: https://lore.kernel.org/all/20260423053102.3717015-1-frankljpliu@gmail.com/
---
Fixes: 4ca0d340ce20 ("perf annotate: Fix instruction association and parsing for LoongArch")
Signed-off-by: Jianping Liu <frankjpliu@tencent.com>
Reviewed-by: Ming Wang <wangming01@loongson.cn>
======================
- Arnaldo
next prev parent reply other threads:[~2026-09-24 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 22:36 Mark Brown
2026-09-24 22:41 ` Arnaldo Melo
2026-09-24 22:48 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-30 10:18 Mark Brown
2026-06-30 10:23 ` Arnaldo Melo
2026-06-30 11:43 ` Arnaldo Carvalho de Melo
2026-06-30 11:44 ` Mark Brown
2026-06-30 17:14 ` Namhyung Kim
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=arWoqiABqzp3Zn6x@x2 \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=broonie@kernel.org \
--cc=frankjpliu@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=wangming01@loongson.cn \
/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
all inboxes | Powered by JetHome®