From: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <kbusch@kernel.org>,
"Wunderlich, Mark" <mark.wunderlich@intel.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/2] nvme-tcp: Set SO_PRIORITY for all sockets
Date: Thu, 30 Jan 2020 14:51:13 -0800 [thread overview]
Message-ID: <a82b08e9-75bd-e14b-7d30-7414df1c90c4@grimberg.me> (raw)
In-Reply-To: <675e24bb-8a91-6612-887a-2a0a38a57cda@grimberg.me>
Keith,
Unless there is any other feedback, I suggest we queue it for
5.6 perhaps?
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-01-30 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 0:46 [PATCH 0/2] nvme-tcp: Set SO_PRIORITY for all sockets Wunderlich, Mark
2020-01-17 1:13 ` Sagi Grimberg
2020-01-30 22:51 ` Sagi Grimberg [this message]
2020-01-31 0:48 ` Keith Busch
2020-02-11 20:31 ` Keith Busch
2020-02-12 20:02 ` 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=a82b08e9-75bd-e14b-7d30-7414df1c90c4@grimberg.me \
--to=sagi@grimberg.me \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mark.wunderlich@intel.com \
/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).