From: Mark Brown <broonie@kernel.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Missing signoff in the perf tree
Date: Sun, 25 Oct 2026 23:36:30 +0000 [thread overview]
Message-ID: <at6Sfv6lR0OivudT@sirena.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
Commits
dc953bd97bb34 ("perf annotate-arm64: Support 'mrs' instruction to track 'current' pointer")
1def3501db416 ("perf annotate-arm64: Support per-cpu variable access tracking")
57758d7a45a91 ("perf annotate-arm64: Support 'adrp' instruction to track global variables")
3de720ecddd77 ("perf annotate-arm64: Support 'add' instruction tracking")
2a4d31c97bc48 ("perf annotate-arm64: Support 'mov' instruction tracking")
5e5337b32bedb ("perf annotate-arm64: Support stack variable tracking")
afd3a56ecd8f5 ("perf annotate-x86: Delete stale stack state on store of untracked register")
7987f78199231 ("perf annotate-data: Track imm_value for stack variables")
c5aec1fbc2e04 ("perf annotate-data: Expand type_state_reg imm_value to u64")
2e1cc4301709a ("perf annotate-arm64: Support store instruction tracking")
5494c4435efc3 ("perf annotate-arm64: Support load instruction tracking")
0bceda338113b ("perf annotate-arm64: Track return type after call instructions")
de5c01e94fca8 ("perf annotate-data: Add arch_get_reg_offset helper")
84c86dc5b867b ("perf annotate-arm64: Enable instruction tracking support")
a21442643267d ("perf annotate-data: Extract invalidate_reg_state() as a common helper")
9b435ebe2ddd6 ("perf cs-etm: Respect --no-itrace option")
6cbb0a8996ef7 ("perf cs-etm: Synthesize missing HW_ID mappings for raw trace")
934d015b78e04 ("perf cs-etm: Free partially created queues")
a965f5ed75bfb ("perf cs-etm: Don't add global v0 HW_IDs to unformatted queues")
895ec1c47eac8 ("perf c2c: Fix memory leaks on output fields")
are missing a Signed-off-by from their committers
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-10-25 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 23:36 Mark Brown [this message]
2026-10-26 0:49 ` Arnaldo Melo
-- strict thread matches above, loose matches on Subject: below --
2026-09-24 22:36 Mark Brown
2026-09-24 22:41 ` Arnaldo Melo
2026-09-24 22:48 ` Arnaldo Carvalho de Melo
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=at6Sfv6lR0OivudT@sirena.co.uk \
--to=broonie@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@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
all inboxes | Powered by JetHome®