From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Ian Rogers <irogers@google.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [FYI] [PATCH] merge resolution commit for perf trace beauty conflict
Date: Thu, 21 May 2026 20:43:11 -0300 [thread overview]
Message-ID: <ag-Yj3p4q0gag4tf@x1> (raw)
In-Reply-To: <ag9G9nKxz8JsiUQc@google.com>
On Thu, May 21, 2026 at 10:55:02AM -0700, Namhyung Kim wrote:
> On Thu, May 21, 2026 at 02:09:14PM -0300, Arnaldo Carvalho de Melo wrote:
> > Just FYI, this is the merge commit solving this conflict.
> >
> > Author: Arnaldo Carvalho de Melo <acme@redhat.com>
> > commit 86c8774ce08b931debdaa3f61f5a033639c183ca
> > Merge: f8d0db39bcc536ef 758c807bb943138f
> > Merge remote-tracking branch 'torvalds/master' into perf-tools-next
> >
> > Fixup clash of:
> >
> > 552636b9317c8a84 ("perf trace: Add beautifier script for fsmount flags")
> >
> > That went via Namhyung upstream and the following ones in the
> > perf-tools-next tree:
> >
> > 32969ef6e3e1979a ("perf build: Pre-generate BPF skeleton tooling during umbrella prepare phase")
> > 537609924c43715e ("perf trace beauty: Make beauty generated C code standalone .o files")
> >
> > This complements sent by Ian Rogers.
>
> As long as you have this with Ian's fix,
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Yeah, that is the case, justg added your Acked-by, thanks for checking
and providing it!
- Arnaldo
next prev parent reply other threads:[~2026-05-21 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 17:09 [FYI] [PATCH] merge resolution commit for perf trace beauty conflict Arnaldo Carvalho de Melo
2026-05-21 17:55 ` Namhyung Kim
2026-05-21 23:43 ` Arnaldo Carvalho de Melo [this message]
2026-05-21 17:58 ` Arnaldo Carvalho de Melo
2026-05-21 18:46 ` Ian Rogers
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=ag-Yj3p4q0gag4tf@x1 \
--to=acme@kernel.org \
--cc=broonie@kernel.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@leemhuis.info \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.