From: kajoljain <kjain@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org,
maddy@linux.vnet.ibm.com, santosh@fossix.org,
aneesh.kumar@linux.ibm.com, vaibhav@linux.ibm.com,
dan.j.williams@intel.com, ira.weiny@intel.com,
atrajeev@linux.vnet.ibm.com, tglx@linutronix.de,
rnsastry@linux.ibm.com
Subject: Re: [PATCH v3 0/4] Add perf interface to expose nvdimm
Date: Wed, 23 Jun 2021 13:40:38 +0530 [thread overview]
Message-ID: <cea827fe-62d4-95fe-b81f-5c7bebe4a6f0@linux.ibm.com> (raw)
In-Reply-To: <YNHiRO11E9yYS6mv@hirez.programming.kicks-ass.net>
On 6/22/21 6:44 PM, Peter Zijlstra wrote:
> On Thu, Jun 17, 2021 at 06:56:13PM +0530, Kajol Jain wrote:
>> ---
>> Kajol Jain (4):
>> drivers/nvdimm: Add nvdimm pmu structure
>> drivers/nvdimm: Add perf interface to expose nvdimm performance stats
>> powerpc/papr_scm: Add perf interface support
>> powerpc/papr_scm: Document papr_scm sysfs event format entries
>
> Don't see anything obviously wrong with this one.
>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
Hi Peter,
Thanks for reviewing the patch. Can you help me on how to take
these patches to linus tree or can you take it?
Thanks,
Kajol Jain
next prev parent reply other threads:[~2021-06-23 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 13:26 [PATCH v3 0/4] Add perf interface to expose nvdimm Kajol Jain
2021-06-17 13:26 ` [PATCH v3 1/4] drivers/nvdimm: Add nvdimm pmu structure Kajol Jain
2021-06-17 13:26 ` [PATCH v3 2/4] drivers/nvdimm: Add perf interface to expose nvdimm performance stats Kajol Jain
2021-06-17 13:26 ` [PATCH v3 3/4] powerpc/papr_scm: Add perf interface support Kajol Jain
2021-06-17 13:26 ` [PATCH v3 4/4] powerpc/papr_scm: Document papr_scm sysfs event format entries Kajol Jain
2021-06-22 13:14 ` [PATCH v3 0/4] Add perf interface to expose nvdimm Peter Zijlstra
2021-06-23 8:10 ` kajoljain [this message]
2021-06-23 8:31 ` Peter Zijlstra
2021-06-23 11:16 ` Michael Ellerman
2021-07-06 7:20 ` kajoljain
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=cea827fe-62d4-95fe-b81f-5c7bebe4a6f0@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nvdimm@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rnsastry@linux.ibm.com \
--cc=santosh@fossix.org \
--cc=tglx@linutronix.de \
--cc=vaibhav@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).