From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>
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-current tree
Date: Wed, 17 Jul 2024 07:50:09 +1000 [thread overview]
Message-ID: <20240717075009.64e73349@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 299 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
1059fb529114 ("perf dsos: When adding a dso into sorted dsos maintain the sort order")
feaaa8be0b1e ("perf comm str: Avoid sort during insert")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-07-16 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 21:50 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-04 21:43 linux-next: duplicate patches in the perf-current tree Stephen Rothwell
2023-09-05 16:40 ` Arnaldo Carvalho de Melo
2023-09-06 0:53 ` Palmer Dabbelt
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=20240717075009.64e73349@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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