From: Christoph Hellwig <hch@lst.de>
To: Varun Prakash <varun@chelsio.com>
Cc: sagi@grimberg.me, hch@lst.de, kbusch@kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 1/2] nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t()
Date: Tue, 23 Nov 2021 17:23:55 +0100 [thread overview]
Message-ID: <20211123162355.GF23957@lst.de> (raw)
In-Reply-To: <1637665136-3563-1-git-send-email-varun@chelsio.com>
Thanks,
applied to nvme-5.16.
prev parent reply other threads:[~2021-11-23 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 10:58 [PATCH v2 1/2] nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t() Varun Prakash
2021-11-23 12:53 ` Sagi Grimberg
2021-11-23 16:23 ` Christoph Hellwig [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=20211123162355.GF23957@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=varun@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