From: Greg KH <greg@kroah.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable-5.0+ v2 1/3] nvme-tcp: rename function to have nvme_tcp prefix
Date: Thu, 20 Jun 2019 16:17:59 +0200 [thread overview]
Message-ID: <20190620141759.GC9832@kroah.com> (raw)
In-Reply-To: <20190617173352.1902-1-sagi@grimberg.me>
On Mon, Jun 17, 2019 at 10:33:50AM -0700, Sagi Grimberg wrote:
> Upstream commit: efb973b19b88 ("nvme-tcp: rename function to have
> nvme_tcp prefix")
>
> usually nvme_ prefix is for core functions.
> While we're cleaning up, remove redundant empty lines
>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> Reviewed-by: Minwoo Im <minwoo.im@samsung.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> drivers/nvme/host/tcp.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
All 3 now queued up, thanks.
greg k-h
prev parent reply other threads:[~2019-06-20 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 17:33 [PATCH stable-5.0+ v2 1/3] nvme-tcp: rename function to have nvme_tcp prefix Sagi Grimberg
2019-06-17 17:33 ` [PATCH stable-5.0+ v2 2/3] nvme-tcp: fix possible null deref on a timed out io queue connect Sagi Grimberg
2019-06-17 17:33 ` [PATCH stable-5.0+ v2 3/3] nvme-tcp: fix queue mapping when queue count is limited Sagi Grimberg
2019-06-20 14:17 ` Greg KH [this message]
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=20190620141759.GC9832@kroah.com \
--to=greg@kroah.com \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.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).