From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>,
"David Ahern" <dsahern@gmail.com>,
"David Woodhouse" <dwmw@amazon.co.uk>,
"Ilya Pronin" <ipronin@twitter.com>,
"Jin Yao" <yao.jin@intel.com>, "Jiri Olsa" <jolsa@redhat.com>,
"Kan Liang" <kan.liang@intel.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Sangwon Hong" <qpakzk@gmail.com>,
stable@vger.kernel.org, "Taeung Song" <treeze.taeung@gmail.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Wang Nan" <wangnan0@huawei.>
Subject: Re: [GIT PULL 0/9] perf/urgent fixes
Date: Wed, 7 Mar 2018 11:23:35 -0300 [thread overview]
Message-ID: <20180307142335.GF3701@kernel.org> (raw)
In-Reply-To: <20180307082258.ldhidzjvdekhhi5g@gmail.com>
Em Wed, Mar 07, 2018 at 09:22:58AM +0100, Ingo Molnar escreveu:
> Pulled, thanks a lot Arnaldo!
> Note that there's a new, minor conflict between perf/core and perf/urgent - I
> resolved it and merged perf/urgent into perf/core, please double check my
> resolution.
Thanks, everything seems well and dandy,
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>,
"David Ahern" <dsahern@gmail.com>,
"David Woodhouse" <dwmw@amazon.co.uk>,
"Ilya Pronin" <ipronin@twitter.com>,
"Jin Yao" <yao.jin@intel.com>, "Jiri Olsa" <jolsa@redhat.com>,
"Kan Liang" <kan.liang@intel.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Sangwon Hong" <qpakzk@gmail.com>,
stable@vger.kernel.org, "Taeung Song" <treeze.taeung@gmail.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
"Wang Nan" <wangnan0@huawei.com>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [GIT PULL 0/9] perf/urgent fixes
Date: Wed, 7 Mar 2018 11:23:35 -0300 [thread overview]
Message-ID: <20180307142335.GF3701@kernel.org> (raw)
In-Reply-To: <20180307082258.ldhidzjvdekhhi5g@gmail.com>
Em Wed, Mar 07, 2018 at 09:22:58AM +0100, Ingo Molnar escreveu:
> Pulled, thanks a lot Arnaldo!
> Note that there's a new, minor conflict between perf/core and perf/urgent - I
> resolved it and merged perf/urgent into perf/core, please double check my
> resolution.
Thanks, everything seems well and dandy,
- Arnaldo
next prev parent reply other threads:[~2018-03-07 14:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 17:23 [GIT PULL 0/9] perf/urgent fixes Arnaldo Carvalho de Melo
2018-03-06 17:23 ` Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 1/9] perf kallsyms: Fix the usage on the man page Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 2/9] perf top: Fix annoying fallback message on older kernels Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 3/9] perf annotate browser: Be more robust when drawing jump arrows Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 4/9] perf record: Fix crash in pipe mode Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 5/9] tools headers: Sync copy of kvm UAPI headers Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 6/9] tools headers: Sync x86's cpufeatures.h Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 7/9] perf stat: Fix CVS output format for non-supported counters Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 8/9] perf auxtrace: Prevent decoding when --no-itrace Arnaldo Carvalho de Melo
2018-03-06 17:23 ` [PATCH 9/9] perf tools: Fix trigger class trigger_on() Arnaldo Carvalho de Melo
2018-03-07 8:22 ` [GIT PULL 0/9] perf/urgent fixes Ingo Molnar
2018-03-07 8:22 ` Ingo Molnar
2018-03-07 14:23 ` Arnaldo Carvalho de Melo [this message]
2018-03-07 14:23 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2019-12-16 20:47 Arnaldo Carvalho de Melo
2019-12-17 11:28 ` Ingo Molnar
2017-09-12 19:24 Arnaldo Carvalho de Melo
2017-09-13 7:26 ` Ingo Molnar
2015-01-21 15:01 Arnaldo Carvalho de Melo
2015-01-28 14:42 ` Ingo Molnar
2013-09-19 18:40 Arnaldo Carvalho de Melo
2013-09-20 5:15 ` Ingo Molnar
2012-03-30 16:09 Arnaldo Carvalho de Melo
2012-03-31 7:31 ` Ingo Molnar
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=20180307142335.GF3701@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=dwmw@amazon.co.uk \
--cc=ipronin@twitter.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=qpakzk@gmail.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.org \
--cc=treeze.taeung@gmail.com \
--cc=wangnan0@huawei. \
--cc=xiyou.wangcong@gmail.com \
--cc=yao.jin@intel.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.