From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Sam Li" <faithilikerun@gmail.com>,
qemu-devel@nongnu.org, stefanha@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>, "Fam Zheng" <fam@euphon.net>,
"Hanna Reitz" <hreitz@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
hare@suse.de, damien.lemoal@opensource.wdc.com,
dmitry.fomichev@wdc.com, qemu-block@nongnu.org
Subject: Re: [PATCH v18 0/8] Add support for zoned device
Date: Mon, 3 Apr 2023 11:28:56 -0400 [thread overview]
Message-ID: <CAJSP0QWj4w5rhFZEw4asJ2oyidEbdhDeD+98j1zf67QRPBTdrg@mail.gmail.com> (raw)
In-Reply-To: <41f2ee75-0465-94d4-90bb-7289e49fdb5d@linaro.org>
Thanks, applied with Philippe's suggested commit message changes:
https://gitlab.com/stefanha/qemu/-/tree/block-next
I left the trace events commit separate.
Stefan
prev parent reply other threads:[~2023-04-03 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 9:05 [PATCH v18 0/8] Add support for zoned device Sam Li
2023-03-24 9:05 ` [PATCH v18 1/8] include: add zoned device structs Sam Li
2023-03-24 9:05 ` [PATCH v18 2/8] file-posix: introduce helper functions for sysfs attributes Sam Li
2023-03-24 9:06 ` [PATCH v18 3/8] block: add block layer APIs resembling Linux ZonedBlockDevice ioctls Sam Li
2023-03-24 9:06 ` [PATCH v18 4/8] raw-format: add zone operations to pass through requests Sam Li
2023-03-24 9:06 ` [PATCH v18 5/8] config: add check to block layer Sam Li
2023-03-24 9:06 ` [PATCH v18 6/8] qemu-iotests: test new zone operations Sam Li
2023-03-24 9:06 ` [PATCH v18 7/8] block: add some trace events for new block layer APIs Sam Li
2023-03-24 9:06 ` [PATCH v18 8/8] docs/zoned-storage: add zoned device documentation Sam Li
2023-03-24 11:26 ` [PATCH v18 0/8] Add support for zoned device Philippe Mathieu-Daudé
2023-04-03 15:28 ` Stefan Hajnoczi [this message]
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=CAJSP0QWj4w5rhFZEw4asJ2oyidEbdhDeD+98j1zf67QRPBTdrg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=berrange@redhat.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dmitry.fomichev@wdc.com \
--cc=faithilikerun@gmail.com \
--cc=fam@euphon.net \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).