From: bharat@chelsio.com (Potnuri Bharat Teja)
Subject: [PATCH] nvme-tcp: Use protocol specific operations while reading socket
Date: Wed, 24 Jul 2019 12:32:45 +0530 [thread overview]
Message-ID: <20190724070244.GB25528@chelsio.com> (raw)
In-Reply-To: <20190724070107.GA2450@lst.de>
On Wednesday, July 07/24/19, 2019@09:01:07 +0200, Christoph Hellwig wrote:
> On Wed, Jul 24, 2019@12:28:59PM +0530, Potnuri Bharat Teja wrote:
> > > > Hi Sagi/Christoph,
> > > > Can this be queued for rc?
> > >
> > > How is this a -rc candidate? I was planning on queuing it up for 5.4444.
> > I believe its a trivial one, so was hoping it could get into immediate rc(rc-2).
> > If you think otherwise I am fine with 5.4 also.
>
> It does look trivial, but that isn't really the criteria for rc time
> inclusion, the prime criteria is if is an important bug fix.
Agreed.
next prev parent reply other threads:[~2019-07-24 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 9:52 [PATCH] nvme-tcp: Use protocol specific operations while reading socket Potnuri Bharat Teja
2019-07-24 6:28 ` Potnuri Bharat Teja
2019-07-24 6:33 ` Christoph Hellwig
2019-07-24 6:58 ` Potnuri Bharat Teja
2019-07-24 7:01 ` Christoph Hellwig
2019-07-24 7:02 ` Potnuri Bharat Teja [this message]
2019-07-24 18:16 ` 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=20190724070244.GB25528@chelsio.com \
--to=bharat@chelsio.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