From: Christoph Hellwig <hch@infradead.org>
To: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme-core: get rid of the unused variable
Date: Mon, 2 Sep 2019 09:14:33 -0700 [thread overview]
Message-ID: <20190902161433.GC27231@infradead.org> (raw)
In-Reply-To: <20190831001013.8581-1-chaitanya.kulkarni@wdc.com>
On Fri, Aug 30, 2019 at 05:10:13PM -0700, Chaitanya Kulkarni wrote:
> void nvme_complete_rq(struct request *req)
> {
> blk_status_t status = nvme_error_status(req);
> - struct nvme_ns *ns = req->q->queuedata;
>
> trace_nvme_complete_rq(req);
I don't actually see this variable in Linus' tree or the nvme-5.4
branch, what tree is this against?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-09-02 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 0:10 [PATCH] nvme-core: get rid of the unused variable Chaitanya Kulkarni
2019-09-01 8:20 ` Max Gurtovoy
2019-09-02 16:14 ` Christoph Hellwig [this message]
2019-09-04 18:27 ` 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=20190902161433.GC27231@infradead.org \
--to=hch@infradead.org \
--cc=chaitanya.kulkarni@wdc.com \
--cc=linux-nvme@lists.infradead.org \
/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).