From: Christoph Hellwig <hch@lst.de>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: brauner@kernel.org, djwong@kernel.org, hyc.lee@gmail.com,
willy@infradead.org, xiang@kernel.org, hch@lst.de,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] iomap: remove over-strict inline data boundary check
Date: Fri, 24 Apr 2026 15:30:01 +0200 [thread overview]
Message-ID: <20260424133001.GA16307@lst.de> (raw)
In-Reply-To: <20260423213203.5533-2-linkinjeon@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-04-24 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 21:32 [PATCH 0/2] iomap/ntfs: remove over-strict inline data check and optimize ntfs Namjae Jeon
2026-04-23 21:32 ` [PATCH 1/2] iomap: remove over-strict inline data boundary check Namjae Jeon
2026-04-24 13:30 ` Christoph Hellwig [this message]
2026-04-24 15:06 ` Gao Xiang
2026-04-23 21:32 ` [PATCH 2/2] ntfs: use direct pointer for inline data to avoid redundant allocation Namjae Jeon
2026-04-24 13:30 ` Christoph Hellwig
2026-04-25 18:37 ` DaeMyung Kang
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=20260424133001.GA16307@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xiang@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