From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Ingo Molnar" <mingo@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Jiri Olsa" <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Clark Williams" <williams@redhat.com>,
"Kate Carcia" <kcarcia@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>,
"Eric Lin" <eric.lin@sifive.com>,
"Ian Rogers" <irogers@google.com>,
"Jesus Sanchez-Palencia" <jesussanp@google.com>,
"Miaoqian Lin" <linmq006@gmail.com>,
"Thomas Richter" <tmricht@linux.ibm.com>,
"Torsten Hilbrich" <torsten.hilbrich@secunet.com>,
"Yang Jihong" <yangjihong1@huawei.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [GIT PULL] perf tools fixes for v6.2: 1st batch
Date: Fri, 6 Jan 2023 14:15:53 -0300 [thread overview]
Message-ID: <Y7hXSQcsAHfG4/yN@kernel.org> (raw)
In-Reply-To: <20230106142256.763489-1-acme@kernel.org>
Em Fri, Jan 06, 2023 at 11:22:56AM -0300, Arnaldo Carvalho de Melo escreveu:
> Hi Linus,
> Please consider pulling, there are some more being tested but
> that should sit in linux-next/pending-fixes for a while.
>
> Please let me know if you think anything should be reworked,
> The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:
> Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)
> are available in the Git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v6.1-1-2023-01-06
Argh, I made a shell history reuse mistake just on the tag name, it
should be, and is available now:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v6.2-1-2023-01-06
- Arnaldo
next prev parent reply other threads:[~2023-01-06 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:22 [GIT PULL] perf tools fixes for v6.2: 1st batch Arnaldo Carvalho de Melo
2023-01-06 17:15 ` Arnaldo Carvalho de Melo [this message]
2023-01-06 21:19 ` pr-tracker-bot
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=Y7hXSQcsAHfG4/yN@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=eric.lin@sifive.com \
--cc=irogers@google.com \
--cc=jesussanp@google.com \
--cc=jolsa@kernel.org \
--cc=kcarcia@redhat.com \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=tmricht@linux.ibm.com \
--cc=torsten.hilbrich@secunet.com \
--cc=torvalds@linux-foundation.org \
--cc=williams@redhat.com \
--cc=yangjihong1@huawei.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 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.