From: Sagi Grimberg <sagi@grimberg.me>
To: Keith Busch <kbusch@kernel.org>
Cc: "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: Wed, 12 Feb 2020 12:02:47 -0800 [thread overview]
Message-ID: <458b2e6a-63af-8fb8-95b3-94083ca09567@grimberg.me> (raw)
In-Reply-To: <20200211203121.GC19458@redsun51.ssa.fujisawa.hgst.com>
>>> Keith,
>>>
>>> Unless there is any other feedback, I suggest we queue it for
>>> 5.6 perhaps?
>>
>> Sounds good, queued up for-5.6.
>
> Sorry all, I did this a little to late for the 5.6 merge window. I've
> started a 5.7 branch and collecting patches there.
That is fine.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-02-12 20:02 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
2020-01-31 0:48 ` Keith Busch
2020-02-11 20:31 ` Keith Busch
2020-02-12 20:02 ` Sagi Grimberg [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=458b2e6a-63af-8fb8-95b3-94083ca09567@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).