From: Karel Zak <kzak@redhat.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: util-linux@vger.kernel.org, Hans Holmberg <hans.holmberg@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH RFC] blkzone: add capacity field to zone report
Date: Mon, 29 Jun 2020 13:11:59 +0200 [thread overview]
Message-ID: <20200629111159.rrpml3hnpmldczap@ws.net.home> (raw)
In-Reply-To: <20200626121225.428611-1-shinichiro.kawasaki@wdc.com>
On Fri, Jun 26, 2020 at 09:12:25PM +0900, Shin'ichiro Kawasaki wrote:
> configure.ac | 4 ++++
> sys-utils/blkzone.8 | 1 +
> sys-utils/blkzone.c | 20 ++++++++++++++++++--
> 3 files changed, 23 insertions(+), 2 deletions(-)
Applied to the "next" branch (for v2.36 is too late). Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2020-06-29 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 12:12 [PATCH RFC] blkzone: add capacity field to zone report Shin'ichiro Kawasaki
2020-06-29 11:11 ` Karel Zak [this message]
2020-07-01 11:32 ` Shinichiro Kawasaki
2020-07-01 11:58 ` Karel Zak
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=20200629111159.rrpml3hnpmldczap@ws.net.home \
--to=kzak@redhat.com \
--cc=Damien.LeMoal@wdc.com \
--cc=hans.holmberg@wdc.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=util-linux@vger.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;
as well as URLs for NNTP newsgroup(s).