[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq17e221vvt.fsf@oracle.com>
Date: Tue, 07 Jan 2020 22:15:34 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: "Singh\, Balbir" <sblbir@...zon.com>
Cc: "martin.petersen\@oracle.com" <martin.petersen@...cle.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block\@vger.kernel.org" <linux-block@...r.kernel.org>,
"Sangaraju\, Someswarudu" <ssomesh@...zon.com>,
"jejb\@linux.ibm.com" <jejb@...ux.ibm.com>,
"hch\@lst.de" <hch@....de>, "axboe\@kernel.dk" <axboe@...nel.dk>,
"mst\@redhat.com" <mst@...hat.com>,
"linux-nvme\@lists.infradead.org" <linux-nvme@...ts.infradead.org>,
"Chaitanya.Kulkarni\@wdc.com" <Chaitanya.Kulkarni@....com>
Subject: Re: [resend v1 1/5] block/genhd: Notify udev about capacity change
Balbir,
> I did this to avoid having to enforce that set_capacity() implied a
> notification. Largely to control the impact of the change by default.
What I thought. I'm OK with set_capacity_and_notify(), btw.
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists