From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@redhat.com>
Cc: <jacob.w.shin@gmail.com>, Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Hurwitz, Sherry" <sherry.hurwitz@amd.com>
Subject: PING: [PATCH V5 0/3] perf/x86/amd: AMD Family 16h Data Breakpoint Extensions
Date: Mon, 21 Oct 2013 11:20:58 -0500 [thread overview]
Message-ID: <5265546A.3000204@amd.com> (raw)
Note: Resend due to error in sending email to the mailing list.
Hi Frederic, Ingo
I am following up with the status of the patch set you have asked me to rebased to the latest upstream kernel.
- I have sent it out on Oct 2nd (here http://marc.info/?l=linux-kernel&m=138073029218979&w=2).
- It has been reviewed by Oleg (http://marc.info/?l=linux-kernel&m=138073096019235&w=2).
Thank you,
Suravee
reply other threads:[~2013-10-21 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5265546A.3000204@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=a.p.zijlstra@chello.nl \
--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 \
/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