From: bharat@chelsio.com (Potnuri Bharat Teja)
Subject: [PATCH] nvme-tcp: Use protocol specific operations while reading socket
Date: Wed, 24 Jul 2019 12:28:59 +0530 [thread overview]
Message-ID: <20190724065858.GA25528@chelsio.com> (raw)
In-Reply-To: <20190724063324.GA1999@lst.de>
On Wednesday, July 07/24/19, 2019@08:33:24 +0200, Christoph Hellwig wrote:
> On Wed, Jul 24, 2019@11:58:38AM +0530, Potnuri Bharat Teja wrote:
> > On Monday, July 07/08/19, 2019@15:22:00 +0530, Potnuri Bharat Teja wrote:
> > > Using socket specific read_sock() calls instead of directly calling
> > > tcp_read_sock() helps lld module registered handlers if any, to be called
> > > from nvme-tcp host.
> > > This patch therefore replaces the tcp_read_sock() with socket specific
> > > prot_ops.
> > >
> > > Signed-off-by: Potnuri Bharat Teja <bharat at chelsio.com>
> > > Acked-by: Sagi Grimberg <sagi at grimberg.me>
> > > ---
> > 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.
Thanks.
next prev parent reply other threads:[~2019-07-24 6:58 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 [this message]
2019-07-24 7:01 ` Christoph Hellwig
2019-07-24 7:02 ` Potnuri Bharat Teja
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=20190724065858.GA25528@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.