From: Jiri Olsa <jolsa@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <andi@firstfloor.org>, Oleg Nesterov <oleg@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Vince Weaver <vincent.weaver@maine.edu>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCHv3 0/4] perf, signal x86: Fix breakpoint events overflow handling
Date: Wed, 15 May 2013 21:28:23 +0200 [thread overview]
Message-ID: <20130515192823.GA1091@krava.redhat.com> (raw)
In-Reply-To: <CAFTL4hzFJ1cOvo0p_r0S+TC4cBJqurtfjkg7fYv-Gtrh2wTLkg@mail.gmail.com>
On Wed, May 15, 2013 at 05:44:07PM +0200, Frederic Weisbecker wrote:
> 2013/5/15 Jiri Olsa <jolsa@redhat.com>:
> > On Tue, May 07, 2013 at 02:29:48PM +0200, Jiri Olsa wrote:
> >> On Wed, May 01, 2013 at 05:25:40PM +0200, Jiri Olsa wrote:
> >> > hi,
> >> > sending v3 for initial patchset:
> >> > https://lkml.org/lkml/2013/3/1/324
> >> >
> >> > basically just sending remaining (not pulled) patches,
> >> > with '*-by: *' tags updated.
> >> >
> >> > v3 changes:
> >> > - perf test patches already pulled in
> >> > - added Oleg's Tested-by for signal related patches
> >> > - added Frederic's Reviewed-by for signal related patches
> >> > - added Peter's Reviewed-by for perf patch.
> >>
> >> hi,
> >>
> >> Thomas, Peter,
> >> any chance you could pull this in?
> >>
> >> Ingo,
> >> could you please take the perf change (4/4)?
> >> it's reviewed by PeterZ
> >
> > ping
>
> May be you can set up a branch based on v3.10-rc1 with these patches
> applied on top and send it as a pull request to Ingo (and LKML + other
> people Cc'ed). Your branch is not pullable as is because it seems to
> be based on tip:master (it's not targeted for mainline, just there for
> testing) and moreover an old enough version of it.
thanks for suggestion, will do this next time :)
jirka
next prev parent reply other threads:[~2013-05-15 19:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 15:25 Jiri Olsa
2013-05-01 15:25 ` [PATCH 1/4] signal x86: Propage RF EFLAGS bit throught the signal restore call Jiri Olsa
2013-05-28 12:51 ` [tip:perf/core] x86/signals: Propagate RF EFLAGS bit through " tip-bot for Jiri Olsa
2013-05-01 15:25 ` [PATCH 2/4] signal x86: Clear RF EFLAGS bit for signal handler Jiri Olsa
2013-05-28 12:52 ` [tip:perf/core] x86/signals: " tip-bot for Jiri Olsa
2013-05-01 15:25 ` [PATCH 3/4] signal x86: Merge EFLAGS bit clearing into single statement Jiri Olsa
2013-05-28 12:54 ` [tip:perf/core] x86/signals: Merge EFLAGS bit clearing into a " tip-bot for Jiri Olsa
2013-05-01 15:25 ` [PATCH 4/4] perf: Fix hw breakpoints overflow period sampling Jiri Olsa
2013-05-28 12:56 ` [tip:perf/core] " tip-bot for Jiri Olsa
2013-05-01 15:52 ` [PATCHv3 0/4] perf, signal x86: Fix breakpoint events overflow handling Oleg Nesterov
2013-05-07 12:29 ` Jiri Olsa
2013-05-15 15:04 ` Jiri Olsa
2013-05-15 15:44 ` Frederic Weisbecker
2013-05-15 19:28 ` Jiri Olsa [this message]
2013-05-15 16:52 ` Peter Zijlstra
2013-05-15 19:28 ` Jiri Olsa
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=20130515192823.GA1091@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=andi@firstfloor.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=vincent.weaver@maine.edu \
/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
Powered by JetHome