From: Jens Axboe <axboe@kernel.dk>
To: Anuj gupta <anuj1072538@gmail.com>
Cc: Anuj Gupta <anuj20.g@samsung.com>,
vincent.fu@samsung.com, hch@infradead.org,
martin.petersen@oracle.com, linux-block@vger.kernel.org,
joshi.k@samsung.com
Subject: Re: [PATCH v2] block: fix lbmd_guard_tag_type assignment in FS_IOC_GETLBMD_CAP
Date: Tue, 22 Jul 2025 06:02:00 -0600 [thread overview]
Message-ID: <33dc4507-d1e0-483a-ae89-e916c52356b8@kernel.dk> (raw)
In-Reply-To: <CACzX3Av=CdrHfchof+LXpAS9=0eTAMxjh0Zs_Cu3O3e8nxYDEQ@mail.gmail.com>
On 7/22/25 5:57 AM, Anuj gupta wrote:
>>
>> Where is this sha? It's not in the block or upstream tree, presumably
>> it's in the vfs tree due to it being an fs commit? In which case
>> you should probably CC that side, as this cannot be picked up on
>> the block side.
>>
> Thanks Jens, you're right ? the original patch went through the VFS
> tree. I'll resend the patch and CC Christian and fsdevel accordingly so
> that it can be routed through the correct tree.
Sounds good, otherwise I don't think it's going anywhere. You can add
Reviewed-by: Jens Axboe <axboe@kernel.dk>
as well.
--
Jens Axboe
next prev parent reply other threads:[~2025-07-22 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250722091328epcas5p4c8707b75d657da9e0590ba634977d71e@epcas5p4.samsung.com>
2025-07-22 9:13 ` [PATCH v2] block: fix lbmd_guard_tag_type assignment in FS_IOC_GETLBMD_CAP Anuj Gupta
2025-07-22 9:14 ` Christoph Hellwig
2025-07-22 11:00 ` Jens Axboe
2025-07-22 11:57 ` Anuj gupta
2025-07-22 12:02 ` Jens Axboe [this message]
2025-07-22 11:04 ` 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=33dc4507-d1e0-483a-ae89-e916c52356b8@kernel.dk \
--to=axboe@kernel.dk \
--cc=anuj1072538@gmail.com \
--cc=anuj20.g@samsung.com \
--cc=hch@infradead.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=vincent.fu@samsung.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 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.