From: Dan Williams <dan.j.williams@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Namhyung Kim <namhyung@kernel.org>
Cc: Liang Kan <kan.liang@linux.intel.com>,
<linux-cxl@vger.kernel.org>, <peterz@infradead.org>,
<mark.rutland@arm.com>, <will@kernel.org>,
<dan.j.williams@intel.com>, <mingo@redhat.com>, <acme@kernel.org>,
<linuxarm@huawei.com>, <linux-perf-users@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
"Dave Jiang" <dave.jiang@intel.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v7 4/5] perf: CXL Performance Monitoring Unit driver
Date: Tue, 30 May 2023 11:19:37 -0700 [thread overview]
Message-ID: <64763e39d9a78_168e29463@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20230530145001.00002560@Huawei.com>
Jonathan Cameron wrote:
>
> Hi,
>
> Tidied up the typos. Thanks,
Care to send that replacement patch? It looks like, in linux-next, no
other tree has picked up:
http://lore.kernel.org/r/20230526095824.16336-2-Jonathan.Cameron@huawei.com
...so I'll queue that as well.
next prev parent reply other threads:[~2023-05-30 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 9:58 [PATCH v7 0/5] perf: CXL 3.0 Performance Monitoring Unit support Jonathan Cameron
2023-05-26 9:58 ` [PATCH v7 1/5] perf: Allow a PMU to have a parent Jonathan Cameron
2023-05-26 9:58 ` [PATCH v7 2/5] cxl: Add functions to get an instance of / count regblocks of a given type Jonathan Cameron
2023-05-30 17:10 ` Dave Jiang
2023-05-26 9:58 ` [PATCH v7 3/5] cxl/pci: Find and register CXL PMU devices Jonathan Cameron
2023-05-26 9:58 ` [PATCH v7 4/5] perf: CXL Performance Monitoring Unit driver Jonathan Cameron
2023-05-27 6:26 ` Namhyung Kim
2023-05-30 13:50 ` Jonathan Cameron
2023-05-30 18:19 ` Dan Williams [this message]
2023-05-31 6:07 ` Namhyung Kim
2023-05-26 9:58 ` [PATCH v7 5/5] docs: perf: Minimal introduction the the CXL PMU device and driver Jonathan Cameron
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=64763e39d9a78_168e29463@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=acme@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®