From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <kbusch@kernel.org>, <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH 0/9] nvme: add helpers and remove duplicate code
Date: Fri, 28 Jan 2022 01:20:06 -0800 [thread overview]
Message-ID: <20220128092015.19289-1-chaitanyak@nvidia.com> (raw)
From: Chaitanya Kulkarni <kch@nvidia.com>
HI,
Instead of opencoding connect_q initialization/error handling and the
initialization of the admin tagset, add common helpers to remove the
ducplicate code in different transports.
-ck
Chaitanya Kulkarni (9):
nvme-fc: add a helper to initialize connect_q
nvme-rdma: use helper to initialize connect_q
nvme-tcp: use helper to initialize connect_q
nvme-loop: use helper to initialize connect_q
nvme-fc: centralize admin tagset initialization
nvme-pci: use helper for tagset initialization
nvme-rdma: use helper for tagset initialization
nvme-tcp: use helper for tagset initialization
nvme-loop: use helper for tagset initialization
drivers/nvme/host/fc.c | 18 +++++-------------
drivers/nvme/host/nvme.h | 25 +++++++++++++++++++++++++
drivers/nvme/host/pci.c | 11 +++--------
drivers/nvme/host/rdma.c | 19 ++++++-------------
drivers/nvme/host/tcp.c | 18 +++++-------------
drivers/nvme/target/loop.c | 19 ++++++-------------
6 files changed, 50 insertions(+), 60 deletions(-)
--
2.29.0
next reply other threads:[~2022-01-28 9:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 9:20 Chaitanya Kulkarni [this message]
2022-01-28 9:20 ` [PATCH 1/9] nvme-fc: add a helper to initialize connect_q Chaitanya Kulkarni
2022-01-28 9:23 ` Chaitanya Kulkarni
2022-01-30 9:44 ` Sagi Grimberg
2022-02-01 8:09 ` Christoph Hellwig
2022-01-28 9:20 ` [PATCH 2/9] nvme-rdma: use " Chaitanya Kulkarni
2022-01-30 9:44 ` Sagi Grimberg
2022-01-28 9:20 ` [PATCH 3/9] nvme-tcp: " Chaitanya Kulkarni
2022-01-30 9:44 ` Sagi Grimberg
2022-01-28 9:20 ` [PATCH 4/9] nvme-loop: " Chaitanya Kulkarni
2022-01-30 9:44 ` Sagi Grimberg
2022-01-28 9:20 ` [PATCH 5/9] nvme-fc: centralize admin tagset initialization Chaitanya Kulkarni
2022-01-28 9:23 ` Chaitanya Kulkarni
2022-01-30 9:47 ` Sagi Grimberg
2022-02-02 6:48 ` Chaitanya Kulkarni
2022-02-01 8:11 ` Christoph Hellwig
2022-02-02 6:46 ` Chaitanya Kulkarni
2022-01-28 9:20 ` [PATCH 6/9] nvme-pci: use helper for " Chaitanya Kulkarni
2022-01-28 9:20 ` [PATCH 7/9] nvme-rdma: " Chaitanya Kulkarni
2022-01-28 9:20 ` [PATCH 8/9] nvme-tcp: " Chaitanya Kulkarni
2022-01-28 9:20 ` [PATCH 9/9] nvme-loop: " Chaitanya Kulkarni
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=20220128092015.19289-1-chaitanyak@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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.