From: Hans Holmberg <Hans.Holmberg@wdc.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Subject: Re: [PATCH v2 5/8] zonefs: Export open zone resource information through sysfs
Date: Wed, 20 Apr 2022 10:52:11 +0000 [thread overview]
Message-ID: <20220420105211.GC36533@gsv> (raw)
In-Reply-To: <20220420023545.3814998-6-damien.lemoal@opensource.wdc.com>
Looks good to me,
Reviewed-by: Hans Holmberg <hans.holmberg@wdc.com>
next prev parent reply other threads:[~2022-04-20 10:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 2:35 [PATCH v2 0/8] zonefs improvements Damien Le Moal
2022-04-20 2:35 ` [PATCH v2 1/8] zonefs: Clear inode information flags on inode creation Damien Le Moal
2022-04-20 3:58 ` Chaitanya Kulkarni
2022-04-20 8:40 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 2/8] zonefs: Fix management of open zones Damien Le Moal
2022-04-20 8:44 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 3/8] zonefs: Rename super block information fields Damien Le Moal
2022-04-20 10:48 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 4/8] zonefs: Always do seq file write open accounting Damien Le Moal
2022-04-20 10:49 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 5/8] zonefs: Export open zone resource information through sysfs Damien Le Moal
2022-04-20 10:52 ` Hans Holmberg [this message]
2022-04-20 2:35 ` [PATCH v2 6/8] zonefs: Add active seq file accounting Damien Le Moal
2022-04-20 7:50 ` Johannes Thumshirn
2022-04-20 10:54 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 7/8] documentation: zonefs: Cleanup the mount options section Damien Le Moal
2022-04-20 10:57 ` Hans Holmberg
2022-04-20 2:35 ` [PATCH v2 8/8] documentation: zonefs: Document sysfs attributes Damien Le Moal
2022-04-20 10:57 ` Hans Holmberg
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=20220420105211.GC36533@gsv \
--to=hans.holmberg@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.