From: Jens Axboe <axboe@kernel.dk>
To: Irvin Cote <irvincoteg@gmail.com>, hch@lst.de
Cc: kbusch@kernel.org, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-pci : redundancies in nvme_alloc_queue and nvme_init_queue
Date: Sat, 20 May 2023 19:48:08 -0600 [thread overview]
Message-ID: <d49afbae-4ce9-5c6f-a1ad-d07f14f2f2b7@kernel.dk> (raw)
In-Reply-To: <20230521000236.100402-1-irvincoteg@gmail.com>
On 5/20/23 6:02 PM, Irvin Cote wrote:
> Signed-off-by: Irvin Cote <irvincoteg@gmail.com>
> ---
> drivers/nvme/host/pci.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 32244582fdb0..49ae26980a0f 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -1533,9 +1533,6 @@ static int nvme_alloc_queue(struct nvme_dev *dev, int qid, int depth)
> nvmeq->dev = dev;
> spin_lock_init(&nvmeq->sq_lock);
> spin_lock_init(&nvmeq->cq_poll_lock);
> - nvmeq->cq_head = 0;
> - nvmeq->cq_phase = 1;
> - nvmeq->q_db = &dev->dbs[qid * 2 * dev->db_stride];
> nvmeq->qid = qid;
> dev->ctrl.queue_count++;
Please put an actual commit message in here, any commit should have
an explanation of WHY the change is being made. Your subject line
is NOT enough, detail exactly why this is redundant.
From a quick look the patch does look fine, but I'm not going to
ack a patch that doesn't have a good commit message.
--
Jens Axboe
next prev parent reply other threads:[~2023-05-21 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 0:02 [PATCH] nvme-pci : redundancies in nvme_alloc_queue and nvme_init_queue Irvin Cote
2023-05-21 1:48 ` Jens Axboe [this message]
2023-05-21 2:36 ` irvin cote
-- strict thread matches above, loose matches on Subject: below --
2023-05-21 2:44 Irvin Cote
2023-05-21 2:46 Irvin Cote
2023-05-21 2:47 ` irvin cote
2023-05-25 15:36 ` Keith Busch
2023-05-25 15:55 ` irvin cote
2023-05-25 18:01 ` Keith Busch
2023-05-21 2:51 [PATCH] nvme-pci: " Irvin Cote
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=d49afbae-4ce9-5c6f-a1ad-d07f14f2f2b7@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=irvincoteg@gmail.com \
--cc=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox