From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me
Cc: baolin.wang7@gmail.com, linux-nvme@lists.infradead.org,
baolin.wang@linux.alibaba.com, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Some cleanups for NVMe-pci driver
Date: Fri, 3 Jul 2020 10:49:19 +0800 [thread overview]
Message-ID: <cover.1593743937.git.baolin.wang@linux.alibaba.com> (raw)
Hi,
These are some cleanups for NVMe-pci driver, and no functional
changes, please help to review. Thanks.
Baolin Wang (5):
nvme-pci: Fix some comments issues
nvme-pci: Add a blank line after declarations
nvme-pci: Remove redundant segment validation
nvme-pci: Use the consistent return type of nvme_pci_iod_alloc_size()
nvme-pci: Use standard block status macro
drivers/nvme/host/pci.c | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
--
1.8.3.1
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me
Cc: baolin.wang@linux.alibaba.com, baolin.wang7@gmail.com,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Some cleanups for NVMe-pci driver
Date: Fri, 3 Jul 2020 10:49:19 +0800 [thread overview]
Message-ID: <cover.1593743937.git.baolin.wang@linux.alibaba.com> (raw)
Hi,
These are some cleanups for NVMe-pci driver, and no functional
changes, please help to review. Thanks.
Baolin Wang (5):
nvme-pci: Fix some comments issues
nvme-pci: Add a blank line after declarations
nvme-pci: Remove redundant segment validation
nvme-pci: Use the consistent return type of nvme_pci_iod_alloc_size()
nvme-pci: Use standard block status macro
drivers/nvme/host/pci.c | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-07-03 2:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 2:49 Baolin Wang [this message]
2020-07-03 2:49 ` [PATCH 0/5] Some cleanups for NVMe-pci driver Baolin Wang
2020-07-03 2:49 ` [PATCH 1/5] nvme-pci: Fix some comments issues Baolin Wang
2020-07-03 2:49 ` Baolin Wang
2020-07-05 6:57 ` Sagi Grimberg
2020-07-05 6:57 ` Sagi Grimberg
2020-07-06 2:10 ` Chaitanya Kulkarni
2020-07-06 2:10 ` Chaitanya Kulkarni
2020-07-03 2:49 ` [PATCH 2/5] nvme-pci: Add a blank line after declarations Baolin Wang
2020-07-03 2:49 ` Baolin Wang
2020-07-05 6:57 ` Sagi Grimberg
2020-07-05 6:57 ` Sagi Grimberg
2020-07-06 2:09 ` Chaitanya Kulkarni
2020-07-06 2:09 ` Chaitanya Kulkarni
2020-07-03 2:49 ` [PATCH 3/5] nvme-pci: Remove redundant segment validation Baolin Wang
2020-07-03 2:49 ` Baolin Wang
2020-07-06 2:23 ` Chaitanya Kulkarni
2020-07-06 2:23 ` Chaitanya Kulkarni
2020-07-03 2:49 ` [PATCH 4/5] nvme-pci: Use the consistent return type of nvme_pci_iod_alloc_size() Baolin Wang
2020-07-03 2:49 ` Baolin Wang
2020-07-05 6:59 ` Sagi Grimberg
2020-07-05 6:59 ` Sagi Grimberg
2020-07-06 2:24 ` Chaitanya Kulkarni
2020-07-06 2:24 ` Chaitanya Kulkarni
2020-07-03 2:49 ` [PATCH 5/5] nvme-pci: Use standard block status macro Baolin Wang
2020-07-03 2:49 ` Baolin Wang
2020-07-05 7:00 ` Sagi Grimberg
2020-07-05 7:00 ` Sagi Grimberg
2020-07-06 2:25 ` Chaitanya Kulkarni
2020-07-06 2:25 ` Chaitanya Kulkarni
2020-07-07 19:01 ` Keith Busch
2020-07-07 19:01 ` Keith Busch
2020-07-08 1:25 ` Baolin Wang
2020-07-08 1:25 ` Baolin Wang
2020-07-08 6:05 ` Christoph Hellwig
2020-07-08 6:05 ` Christoph Hellwig
2020-07-07 8:50 ` [PATCH 0/5] Some cleanups for NVMe-pci driver Christoph Hellwig
2020-07-07 8:50 ` Christoph Hellwig
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=cover.1593743937.git.baolin.wang@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=axboe@fb.com \
--cc=baolin.wang7@gmail.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@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.