From: "Singh, Balbir" <sblbir@amazon.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"=linux-block@vger.kernel.org" <=linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"Sangaraju, Someswarudu" <ssomesh@amazon.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"hch@lst.de" <hch@lst.de>, "mst@redhat.com" <mst@redhat.com>
Subject: Re: [RFC PATCH 1/5] block/genhd: Notify udev about capacity change
Date: Mon, 23 Dec 2019 01:53:40 +0000 [thread overview]
Message-ID: <e452f6a638fe09f065b9e4cd1c25d5d3a2f29e5a.camel@amazon.com> (raw)
In-Reply-To: <20191223014056.17318-1-sblbir@amazon.com>
On Mon, 2019-12-23 at 01:40 +0000, Balbir Singh wrote:
> Allow block/genhd to notify user space (via udev) about disk size changes
> using a new helper disk_set_capacity(), which is a wrapper on top
> of set_capacity(). disk_set_capacity() will only notify via udev if
> the current capacity or the target capacity is not zero.
>
> Background:
>
> As a part of a patch to allow sending the RESIZE event on disk capacity
> change, Christoph (hch@lst.de) requested that the patch be made generic
> and the hacks for virtio block and xen block devices be removed and
> merged via a generic helper.
>
>
I messed up with linux-block ML address, I can resend with the right address
if needed. My apologies
Balbir Singh.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-12-23 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 1:40 [RFC PATCH 1/5] block/genhd: Notify udev about capacity change Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 2/5] drivers/block/virtio_blk.c: Convert to use disk_set_capacity Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 3/5] drivers/block/xen-blkfront.c: " Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 4/5] drivers/nvme/host/core.c: " Balbir Singh
2019-12-23 1:40 ` [RFC PATCH 5/5] drivers/scsi/sd.c: " Balbir Singh
2019-12-23 1:53 ` Singh, Balbir [this message]
2020-01-01 3:26 ` [RFC PATCH 1/5] block/genhd: Notify udev about capacity change Chaitanya Kulkarni
2020-01-02 7:36 ` Singh, Balbir
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=e452f6a638fe09f065b9e4cd1c25d5d3a2f29e5a.camel@amazon.com \
--to=sblbir@amazon.com \
--cc==linux-block@vger.kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mst@redhat.com \
--cc=ssomesh@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).