From: Christoph Hellwig <hch@lst.de>
To: Balbir Singh <sblbir@amazon.com>
Cc: axboe@kernel.dk, Chaitanya.Kulkarni@wdc.com,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, hch@lst.de
Subject: Re: [PATCH v3 4/5] nvme: Convert to use set_capacity_revalidate_and_notify
Date: Fri, 13 Mar 2020 12:10:58 +0100 [thread overview]
Message-ID: <20200313111058.GD8264@lst.de> (raw)
In-Reply-To: <20200313053009.19866-5-sblbir@amazon.com>
On Fri, Mar 13, 2020 at 05:30:08AM +0000, Balbir Singh wrote:
> block/genhd provides set_capacity_revalidate_and_notify() for
> sending RESIZE notifications via uevents. This notification is
> newly added to NVME devices
>
> Signed-off-by: Balbir Singh <sblbir@amazon.com>
> Acked-by: Keith Busch <kbusch@kernel.org>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-13 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 5:30 [PATCH v3 0/5] Add support for block disk resize notification Balbir Singh
2020-03-13 5:30 ` [PATCH v3 1/5] block/genhd: Notify udev about capacity change Balbir Singh
2020-03-13 11:09 ` Christoph Hellwig
2020-03-13 5:30 ` [PATCH v3 2/5] virtio_blk.c: Convert to use set_capacity_revalidate_and_notify Balbir Singh
2020-03-13 11:10 ` Christoph Hellwig
2020-03-13 5:30 ` [PATCH v3 3/5] xen-blkfront.c: " Balbir Singh
2020-03-13 11:10 ` Christoph Hellwig
2020-03-13 5:30 ` [PATCH v3 4/5] nvme: " Balbir Singh
2020-03-13 11:10 ` Christoph Hellwig [this message]
2020-03-13 5:30 ` [PATCH v3 5/5] scsi: " Balbir Singh
2020-03-13 11:11 ` Christoph Hellwig
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=20200313111058.GD8264@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sblbir@amazon.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).