From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dmitry Fomichev <dmitry.fomichev@wdc.com>,
Jens Axboe <axboe@kernel.dk>,
virtio-dev@lists.oasis-open.org,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Sam Li <faithilikerun@gmail.com>,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org
Subject: [virtio-dev] Re: [PATCH v2 1/2] virtio-blk: migrate to the latest patchset version
Date: Mon, 3 Apr 2023 13:35:59 -0400 [thread overview]
Message-ID: <20230403133334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <ZCrtjrYQHnppV8gN@infradead.org>
On Mon, Apr 03, 2023 at 08:15:26AM -0700, Christoph Hellwig wrote:
> What is "migrate to the latest patchset version" even supposed to mean?
>
> I don't think that belongs into a kernel commit description.
I think this should be something like "update to latest interface version".
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-04-03 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:49 [virtio-dev] [PATCH v2 0/2] virtio-blk: fix a few problems in ZBD-related code Dmitry Fomichev
2023-03-30 21:49 ` [virtio-dev] [PATCH v2 1/2] virtio-blk: migrate to the latest patchset version Dmitry Fomichev
[not found] ` <ZCrtjrYQHnppV8gN@infradead.org>
2023-04-03 17:35 ` Michael S. Tsirkin [this message]
2023-04-03 17:53 ` Michael S. Tsirkin
2023-03-30 21:49 ` [virtio-dev] [PATCH v2 2/2] virtio-blk: fix ZBD probe in kernels without ZBD support Dmitry Fomichev
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=20230403133334-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=faithilikerun@gmail.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).