From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Christoph Hellwig <hch@lst.de>,
"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
Jack Wang <jinpu.wang@ionos.com>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH 4/4] rnbd-srv: remove struct rnbd_dev
Date: Tue, 23 Aug 2022 01:10:37 +0000 [thread overview]
Message-ID: <23ae7aa1-928a-04de-cc08-18a0093c8748@nvidia.com> (raw)
In-Reply-To: <20220822061745.152010-5-hch@lst.de>
On 8/21/22 23:17, Christoph Hellwig wrote:
> Given that rnbd_srv_sess_dev already has an open_flags member, there
> is no need for the rnbd_dev indirection as a simple block_device pointer
> works just as well.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
next prev parent reply other threads:[~2022-08-23 1:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 6:17 rnbd cleanups Christoph Hellwig
2022-08-22 6:17 ` [PATCH 1/4] rnbd-srv: simplify rnbd_srv_fill_msg_open_rsp Christoph Hellwig
2022-08-23 1:08 ` Chaitanya Kulkarni
2022-08-22 6:17 ` [PATCH 2/4] rnbd-srv: remove rnbd_endio Christoph Hellwig
2022-08-23 1:09 ` Chaitanya Kulkarni
2022-08-22 6:17 ` [PATCH 3/4] rnbd-srv: remove rnbd_dev_{open,close} Christoph Hellwig
2022-08-23 1:09 ` Chaitanya Kulkarni
2022-08-22 6:17 ` [PATCH 4/4] rnbd-srv: remove struct rnbd_dev Christoph Hellwig
2022-08-23 1:10 ` Chaitanya Kulkarni [this message]
2022-08-22 7:20 ` rnbd cleanups Jinpu Wang
-- strict thread matches above, loose matches on Subject: below --
2022-09-09 13:15 rnbd cleanups v2 Christoph Hellwig
2022-09-09 13:15 ` [PATCH 4/4] rnbd-srv: remove struct rnbd_dev Christoph Hellwig
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=23ae7aa1-928a-04de-cc08-18a0093c8748@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=haris.iqbal@ionos.com \
--cc=hch@lst.de \
--cc=jinpu.wang@ionos.com \
--cc=linux-block@vger.kernel.org \
/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