From: Christoph Hellwig <hch@lst.de>
To: Rikard Falkeborn <rikard.falkeborn@gmail.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-tcp: constify static struct blk_mq_ops
Date: Tue, 9 Jun 2020 15:44:52 +0200 [thread overview]
Message-ID: <20200609134452.GB10030@lst.de> (raw)
In-Reply-To: <20200528222507.390172-1-rikard.falkeborn@gmail.com>
Thanks,
applied to nvme-5.8.
prev parent reply other threads:[~2020-06-09 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 22:25 [PATCH] nvme-tcp: constify static struct blk_mq_ops Rikard Falkeborn
2020-05-28 22:33 ` Sagi Grimberg
2020-05-31 9:04 ` Max Gurtovoy
2020-06-09 13:44 ` 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=20200609134452.GB10030@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=rikard.falkeborn@gmail.com \
--cc=sagi@grimberg.me \
/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).