From: Christoph Hellwig <hch@infradead.org>
To: Anuj Gupta/Anuj Gupta <anuj20.g@samsung.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
vincent.fu@samsung.com, jack@suse.cz, anuj1072538@gmail.com,
axboe@kernel.dk, viro@zeniv.linux.org.uk, brauner@kernel.org,
ebiggers@kernel.org, adilger@dilger.ca,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
joshi.k@samsung.com
Subject: Re: [PATCH for-next v2 2/2] fs: add ioctl to query protection info capabilities
Date: Mon, 9 Jun 2025 22:31:37 -0700 [thread overview]
Message-ID: <aEfDOfnSq7AtiFI5@infradead.org> (raw)
In-Reply-To: <e044bbcf-bfd6-48da-a7cf-e5993287f288@samsung.com>
On Mon, Jun 09, 2025 at 11:14:42AM +0530, Anuj Gupta/Anuj Gupta wrote:
> On 6/9/2025 9:41 AM, Christoph Hellwig wrote:
> > On Thu, Jun 05, 2025 at 10:07:00PM -0400, Martin K. Petersen wrote:
> >>
> >> Hi Anuj!
> >>
> >>> A new structure struct fs_pi_cap is introduced, which contains the
> >>> following fields:
> >>
> >> Maybe fs_metadata_cap and then fmd_ as prefix in the struct?
> >
> > Yeah, that does sound better.
> >
> >
> Based on the recent discussion and suggestion from Martin [1] I was
> planning to use logical_block_metadata_cap instead. Does that idea sound
> fine to you?
It's okay. I find the name a little long, but at least it describes
what is going on.
next prev parent reply other threads:[~2025-06-10 5:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250605150741epcas5p4e5cd0b21137fa714006f44045ff272e2@epcas5p4.samsung.com>
2025-06-05 15:07 ` [PATCH for-next v2 0/2] add ioctl to query protection info capabilities Anuj Gupta
2025-06-05 15:07 ` [PATCH for-next v2 1/2] block: introduce pi_size field in blk_integrity Anuj Gupta
2025-06-06 1:51 ` Martin K. Petersen
2025-06-09 4:10 ` Christoph Hellwig
2025-06-05 15:07 ` [PATCH for-next v2 2/2] fs: add ioctl to query protection info capabilities Anuj Gupta
2025-06-06 2:07 ` Martin K. Petersen
2025-06-06 11:59 ` Anuj gupta
2025-06-06 14:53 ` Martin K. Petersen
2025-06-09 4:11 ` Christoph Hellwig
2025-06-09 5:44 ` Anuj Gupta/Anuj Gupta
2025-06-10 5:31 ` Christoph Hellwig [this message]
2025-06-10 10:26 ` Martin K. Petersen
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=aEfDOfnSq7AtiFI5@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jack@suse.cz \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vincent.fu@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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.