From: Greg KH <gregkh@linuxfoundation.org>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH stable-5.0+ 3/3] nvme-tcp: fix queue mapping when queue count is limited
Date: Fri, 14 Jun 2019 15:40:00 +0200 [thread overview]
Message-ID: <20190614134000.GB1076@kroah.com> (raw)
In-Reply-To: <2efe1238-b183-6a70-25a5-d31666a1df17@grimberg.me>
On Fri, Jun 14, 2019 at 06:29:39AM -0700, Sagi Grimberg wrote:
> Its on its way to Linus...
>
> Should I just respin again once it lands there?
Yes please, there's nothing we can do until then.
greg k-h
next prev parent reply other threads:[~2019-06-14 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 4:58 [PATCH stable-5.0+ 1/3] nvme-tcp: rename function to have nvme_tcp prefix Sagi Grimberg
2019-06-10 4:58 ` [PATCH stable-5.0+ 2/3] nvme-tcp: fix possible null deref on a timed out io queue connect Sagi Grimberg
2019-06-10 20:41 ` Sasha Levin
2019-06-10 4:58 ` [PATCH stable-5.0+ 3/3] nvme-tcp: fix queue mapping when queue count is limited Sagi Grimberg
2019-06-13 7:45 ` Greg KH
2019-06-14 13:29 ` Sagi Grimberg
2019-06-14 13:40 ` Greg KH [this message]
2019-06-14 13:40 ` Greg KH
2019-06-13 7:44 ` [PATCH stable-5.0+ 1/3] nvme-tcp: rename function to have nvme_tcp prefix Greg KH
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=20190614134000.GB1076@kroah.com \
--to=gregkh@linuxfoundation.org \
--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).