From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/1] nvmet: avoid dereferencing nvmet_req
Date: Mon, 23 Jan 2017 19:38:15 +0100 [thread overview]
Message-ID: <20170123183815.GA24026@lst.de> (raw)
In-Reply-To: <1485162072-10335-1-git-send-email-maxg@mellanox.com>
On Mon, Jan 23, 2017@11:01:12AM +0200, Max Gurtovoy wrote:
> No need to dereference req twice to get the cmd when we already
> have it stored in a local variable.
>
> Signed-off-by: Max Gurtovoy <maxg at mellanox.com>
> Reviewed-by: Parav Pandit <parav at mellanox.com>
Looks good (for 4.11)
next prev parent reply other threads:[~2017-01-23 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 9:01 [PATCH 1/1] nvmet: avoid dereferencing nvmet_req Max Gurtovoy
2017-01-23 18:38 ` Christoph Hellwig [this message]
2017-01-23 19:52 ` Sagi Grimberg
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=20170123183815.GA24026@lst.de \
--to=hch@lst.de \
/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