From: Damien Le Moal <damien.lemoal@wdc.com>
To: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 0/2] Small cleanups
Date: Mon, 21 Oct 2019 08:42:18 +0900 [thread overview]
Message-ID: <20191020234220.14888-1-damien.lemoal@wdc.com> (raw)
This is series is a couple of cleanup patches. The first one cleans up
the helper function nvme_block_nr() using SECTOR_SHIFT instead of the
hard coded value 9. The second patch introduces the nvme_block_sect()
helper to convert a device block number into a 512B sector value.
Please consider this series for kernel 5.5.
Damien Le Moal (2):
nvme: Cleanup nvme_block_nr()
nvme: Introduce nvme_block_sect()
drivers/nvme/host/core.c | 14 +++++++-------
drivers/nvme/host/nvme.h | 13 ++++++++++++-
2 files changed, 19 insertions(+), 8 deletions(-)
--
2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <damien.lemoal@wdc.com>
To: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 0/2] Small cleanups
Date: Mon, 21 Oct 2019 08:42:18 +0900 [thread overview]
Message-ID: <20191020234220.14888-1-damien.lemoal@wdc.com> (raw)
This is series is a couple of cleanup patches. The first one cleans up
the helper function nvme_block_nr() using SECTOR_SHIFT instead of the
hard coded value 9. The second patch introduces the nvme_block_sect()
helper to convert a device block number into a 512B sector value.
Please consider this series for kernel 5.5.
Damien Le Moal (2):
nvme: Cleanup nvme_block_nr()
nvme: Introduce nvme_block_sect()
drivers/nvme/host/core.c | 14 +++++++-------
drivers/nvme/host/nvme.h | 13 ++++++++++++-
2 files changed, 19 insertions(+), 8 deletions(-)
--
2.21.0
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-10-20 23:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 23:42 Damien Le Moal [this message]
2019-10-20 23:42 ` [PATCH 0/2] Small cleanups Damien Le Moal
2019-10-20 23:42 ` [PATCH 1/2] nvme: Cleanup nvme_block_nr() Damien Le Moal
2019-10-20 23:42 ` Damien Le Moal
2019-10-21 2:13 ` Bart Van Assche
2019-10-21 2:13 ` Bart Van Assche
2019-10-20 23:42 ` [PATCH 2/2] nvme: Introduce nvme_block_sect() Damien Le Moal
2019-10-20 23:42 ` Damien Le Moal
2019-10-21 2:14 ` Bart Van Assche
2019-10-21 2:14 ` Bart Van Assche
2021-09-29 9:17 [PATCH 0/2] small cleanups Damien Le Moal
2022-01-10 22:04 ` Martin K. Petersen
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=20191020234220.14888-1-damien.lemoal@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.