From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the perf tree
Date: Mon, 8 May 2023 10:53:46 +1000 [thread overview]
Message-ID: <20230508105346.24d4dc39@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
1f30bd499605 ("perf symbols: Fix return incorrect build_id size in elf_read_build_id()")
419bd54a3875 ("perf list: Fix memory leaks in print_tracepoint_events()")
4692917156b2 ("perf script: Print raw ip instead of binary offset for callchain")
494fc963a281 ("perf lock contention: Fix struct rq lock access")
4e05971903f0 ("perf unwind: Suppress massive unsupported target platform errors")
5d27a645f609 ("perf tracepoint: Fix memory leak in is_valid_tracepoint()")
7e5fd3db2371 ("perf lock contention: Rework offset calculation with BPF CO-RE")
aec1164e09cc ("perf script: Add new parameter in kfree_skb tracepoint to the python scripts using it")
db483eee8670 ("perf build: Fix unescaped # in perf build-test")
e7767ec67a10 ("perf cs-etm: Add fix for coresight trace for any range of CPUs")
e7cac3fd8ca6 ("perf list: Modify the warning message about scandirat(3)")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-05-08 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 0:53 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-08 21:57 linux-next: duplicate patches in the perf tree Stephen Rothwell
2024-09-02 0:51 Stephen Rothwell
2024-09-04 22:42 ` Stephen Rothwell
2024-09-05 15:07 ` Arnaldo Carvalho de Melo
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=20230508105346.24d4dc39@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnaldo.melo@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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