From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Pankaj Raghav <p.raghav@samsung.com>
Cc: "Sagi Grimberg" <sagi@grimberg.me>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Jens Axboe" <axboe@kernel.dk>,
"Javier González" <javier.gonz@samsung.com>,
"Adam Manzanares" <a.manzanares@samsung.com>,
"kanchan Joshi" <joshi.k@samsung.com>,
"Keith Busch" <kbusch@kernel.org>,
"Johannes Thumshirn" <johannes.thumshirn@wdc.com>,
"Pankaj Raghav" <pankydev8@gmail.com>,
"Kanchan Joshi" <joshiiitr@gmail.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH v2] nvme: Fix zns drives without append support to export correct permissions
Date: Wed, 16 Mar 2022 09:54:46 +0000 [thread overview]
Message-ID: <9498d380-0172-dae0-9354-bd4d725fff5c@nvidia.com> (raw)
In-Reply-To: <20220316093423.17906-1-p.raghav@samsung.com>
> +static inline void nvme_set_disk_mode_ro(struct nvme_ns *ns)
> +{
> + set_disk_ro(ns->disk, test_bit(NVME_NS_FORCE_RO, &ns->flags));
> +}
> +
Do you have a second caller for above function ?
next prev parent reply other threads:[~2022-03-16 9:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220316093439eucas1p27c2a31849e9dec6c6bc217c5f1b26180@eucas1p2.samsung.com>
2022-03-16 9:34 ` [PATCH v2] nvme: Fix zns drives without append support to export correct permissions Pankaj Raghav
2022-03-16 9:54 ` Chaitanya Kulkarni [this message]
2022-03-16 9:56 ` Chaitanya Kulkarni
2022-03-16 10:21 ` Pankaj Raghav
2022-03-16 16:50 ` Chaitanya Kulkarni
2022-03-16 18:03 ` Pankaj Raghav
2022-03-16 10:50 ` Christoph Hellwig
2022-03-16 14:28 ` Pankaj Raghav
2022-03-22 8:39 ` Christoph Hellwig
2022-03-16 16:52 ` Chaitanya Kulkarni
2022-03-16 18:00 ` Pankaj Raghav
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=9498d380-0172-dae0-9354-bd4d725fff5c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=a.manzanares@samsung.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=johannes.thumshirn@wdc.com \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@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 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.