From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: qemu-devel@nongnu.org, "Fan Ni" <fan.ni@samsung.com>,
linux-cxl@vger.kernel.org, linuxarm@huawei.com,
"Ira Weiny" <ira.weiny@intel.com>,
"Michael Roth" <michael.roth@amd.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Dave Jiang" <dave.jiang@intel.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Mike Maslenkin" <mike.maslenkin@gmail.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v8 0/4] hw/cxl: Poison get, inject, clear
Date: Fri, 23 Jun 2023 02:59:44 -0400 [thread overview]
Message-ID: <20230623025836-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230526170010.574-1-Jonathan.Cameron@huawei.com>
On Fri, May 26, 2023 at 06:00:06PM +0100, Jonathan Cameron wrote:
> v8: Formatting fixes for QMP docs from Markus Armbruster (thanks!)
This and other patches add a bunch of over-80 chars lines. I'm not
going to intervene here as cxl has lots of them but maybe scan over cxl
codebase and shorten where appropriate.
Thanks!
--
MST
next prev parent reply other threads:[~2023-06-23 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 17:00 [PATCH v8 0/4] hw/cxl: Poison get, inject, clear Jonathan Cameron via
2023-05-26 17:00 ` [PATCH v8 1/4] bswap: Add the ability to store to an unaligned 24 bit field Jonathan Cameron via
2024-06-21 7:10 ` Philippe Mathieu-Daudé
2023-05-26 17:00 ` [PATCH v8 2/4] hw/cxl: QMP based poison injection support Jonathan Cameron via
2023-05-26 17:00 ` [PATCH v8 3/4] hw/cxl: Add poison injection via the mailbox Jonathan Cameron via
2023-05-26 17:00 ` [PATCH v8 4/4] hw/cxl: Add clear poison mailbox command support Jonathan Cameron via
2023-06-23 6:59 ` Michael S. Tsirkin [this message]
2023-06-23 12:06 ` [PATCH v8 0/4] hw/cxl: Poison get, inject, clear Jonathan Cameron via
2023-06-23 12:13 ` Peter Maydell
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=20230623025836-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dave.jiang@intel.com \
--cc=eblake@redhat.com \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=mike.maslenkin@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).