From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>, <jacob.w.shin@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tgl@domain.invalid>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>
Subject: Re: [PATCH V4 0/3] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions
Date: Mon, 30 Sep 2013 09:09:47 -0500 [thread overview]
Message-ID: <5249862B.90604@amd.com> (raw)
In-Reply-To: <20130429123051.GA15502@redhat.com>
On 4/29/2013 7:30 AM, Oleg Nesterov wrote:
> On 04/29, Ingo Molnar wrote:
>> * Oleg Nesterov <oleg@redhat.com> wrote:
>>> Obviously I can't ack the changes in this area, but to me the whole
>>> series looks fine.
>> Thanks Oleg - can I add your Reviewed-by tags?
> Yes, sure, thanks,
>
> Reviewed-by: Oleg Nesterov <oleg@redhat.com>
>
Hi All,
I am following up with the status of this patch as I have not seen it
merge upstream yet.
I was working with Jacob, and I can help following up with any pending
issues.
Thank you,
Suravee
next prev parent reply other threads:[~2013-09-30 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 6:05 [PATCH V4 0/3] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions Jacob Shin
2013-04-28 6:05 ` [PATCH 1/3] perf/x86/amd: AMD support for bp_len > HW_BREAKPOINT_LEN_8 Jacob Shin
2013-04-28 6:05 ` [PATCH 2/3] perf tools: allow user to specify hardware breakpoint bp_len Jacob Shin
2013-04-28 6:05 ` [PATCH 3/3] perf tools: add hardware breakpoint bp_len test cases Jacob Shin
2013-04-28 16:31 ` [PATCH V4 0/3] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions Oleg Nesterov
2013-04-29 11:12 ` Ingo Molnar
2013-04-29 12:30 ` Oleg Nesterov
2013-09-30 14:09 ` Suravee Suthikulpanit [this message]
2013-10-01 11:17 ` Frederic Weisbecker
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=5249862B.90604@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jacob.w.shin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=sherry.hurwitz@amd.com \
--cc=tgl@domain.invalid \
/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