From: Stephen Rothwell <sfr@rothwell.id.au>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Ian Rogers <irogers@google.com>,
linux-kernel-next@vger.kernel.org,
linux-perf-users@vger.kernel.org, hca@linux.ibm.com,
egorenar@linux.ibm.com, gor@linux.ibm.com, svens@linux.ibm.com,
sumanthk@linux.ibm.com
Subject: Re: PING Re: [PATCH] tools/perf: Fix perf tool build error in util/pfm.c
Date: Thu, 16 Feb 2023 07:28:15 +1100 [thread overview]
Message-ID: <20230216072815.11dc4779@oak.ozlabs.ibm.com> (raw)
In-Reply-To: <Y+0Hqgb4fFTx9XlX@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi Arnaldo,
On Wed, 15 Feb 2023 13:26:18 -0300 Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> In such cases please CC the linux-next maintainer:
>
> Stephen, can you please merge acme/perf/core into linux-next?
I currently fetch every day and merge
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git branches
perf/urgent and perf/core (as you have asked me to in the past). In
yesterday's linux-next release, the top of those branches were commits
f883675bf652 ("Merge tag 'gpio-fixes-for-v6.2-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux")
and
6a5558f11664 ("perf tools: Fix perf tool build error in util/pfm.c")
respectively. This latter one has not changed today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-02-15 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 14:04 [PATCH] tools/perf: Fix perf tool build error in util/pfm.c Thomas Richter
2023-02-07 15:02 ` Arnaldo Carvalho de Melo
2023-02-08 5:58 ` Ian Rogers
2023-02-08 13:40 ` Arnaldo Carvalho de Melo
2023-02-08 13:44 ` Arnaldo Carvalho de Melo
2023-02-08 14:07 ` Arnaldo Carvalho de Melo
2023-02-15 14:17 ` PING " Thomas Richter
2023-02-15 16:26 ` Arnaldo Carvalho de Melo
2023-02-15 20:28 ` Stephen Rothwell [this message]
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=20230216072815.11dc4779@oak.ozlabs.ibm.com \
--to=sfr@rothwell.id.au \
--cc=acme@kernel.org \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=irogers@google.com \
--cc=linux-kernel-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sumanthk@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=tmricht@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).