From: Mark Brown <broonie@kernel.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
TAKANO Mitsuhiro <takano32@gmail.com>
Subject: linux-next: manual merge of the perf tree with the perf-current tree
Date: Thu, 12 Nov 2026 13:10:59 +0000 [thread overview]
Message-ID: <avW648YFgbci03ra@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
Hi all,
Today's linux-next merge of the perf tree got a conflict in:
tools/perf/pmu-events/arch/arm64/ampere/ampereonex/memory.json
between commit:
a89a17e152c8e ("perf vendor events arm64 AmpereOneX: Deprecate BPU_FLUSH_MEM_FAULT")
from the perf-current tree and commit:
294b096cafe17 ("perf vendor events arm64 AmpereOneX: Deprecate BPU_FLUSH_MEM_FAULT")
from the perf tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
The -next copy of the cherry pick has an extra '.'.
diff --combined tools/perf/pmu-events/arch/arm64/ampere/ampereonex/memory.json
index 114f95e41e0d5,b0934a7b252c3..0000000000000
--- a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/memory.json
+++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/memory.json
@@@ -35,7 -35,7 +35,7 @@@
"ArchStdEvent": "MEM_ACCESS_CHECKED_WR"
},
{
- "PublicDescription": "This event is deprecated. Refer to new event GPC_FLUSH_MEM_FAULT. Flushes due to memory hazards",
+ "PublicDescription": "This event is deprecated. Refer to new event GPC_FLUSH_MEM_FAULT Flushes due to memory hazards",
"EventCode": "0x121",
"EventName": "BPU_FLUSH_MEM_FAULT",
"BriefDescription": "This event is deprecated. Refer to new event GPC_FLUSH_MEM_FAULT",
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-11-12 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 13:10 Mark Brown [this message]
2026-11-12 15:29 ` TAKANO Mitsuhiro
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=avW648YFgbci03ra@sirena.org.uk \
--to=broonie@kernel.org \
--cc=acme@redhat.com \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=takano32@gmail.com \
/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®