From: "Singh, Balbir" <sblbir@amazon.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chaitanya.Kulkarni@wdc.com" <Chaitanya.Kulkarni@wdc.com>,
"=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: Thu, 2 Jan 2020 07:36:18 +0000 [thread overview]
Message-ID: <507d6d24a15b76c9887b1746db37f4dc970e7800.camel@amazon.com> (raw)
In-Reply-To: <BYAPR04MB5749C2F13BD6F6C15509FE8586210@BYAPR04MB5749.namprd04.prod.outlook.com>
On Wed, 2020-01-01 at 03:26 +0000, Chaitanya Kulkarni wrote:
> On 12/22/19 5:53 PM, Singh, Balbir wrote:
> > I messed up with linux-block ML address, I can resend with the right
> > address
> > if needed. My apologies
> >
> > Balbir Singh.
>
>
> Unless you have sent it already and I totally missed it,
> if you are planning to resend can you please also add a cover-letter ?
I did not resend it, I'll resend and add a cover letter.
Balbir Singh.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-01-02 7:36 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 ` [RFC PATCH 1/5] block/genhd: Notify udev about capacity change Singh, Balbir
2020-01-01 3:26 ` Chaitanya Kulkarni
2020-01-02 7:36 ` Singh, Balbir [this message]
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=507d6d24a15b76c9887b1746db37f4dc970e7800.camel@amazon.com \
--to=sblbir@amazon.com \
--cc==linux-block@vger.kernel.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--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).