From: Hyunchul Lee <hyc.lee@gmail.com>
To: liubaolin <liubaolin12138@163.com>
Cc: linkinjeon@kernel.org, ntfs@lists.linux.dev,
linux-kernel@vger.kernel.org, chenxiaosong@chenxiaosong.com,
Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v4 00/10] ntfs: persist Linux file attributes in an EA
Date: Mon, 12 Oct 2026 13:43:11 +0900 [thread overview]
Message-ID: <asxlX7ysgW7--bE5@hyunchul-PC02> (raw)
In-Reply-To: <1385152d-9e3d-46da-9a3a-299ad60d521c@163.com>
Hi Baolin,
>
> Hi Namjae and Hyunchul,
> Are there any remaining concerns or changes needed for this patch
> series?
> I'd be happy to address any feedback.
No, I think he maybe have missed these series.
>
> Thanks,
> Baolin.
>
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-10-12 4:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 6:02 Baolin Liu
2026-09-23 6:02 ` [PATCH v4 01/10] ntfs: keep the EA presence flag after creating the first entry Baolin Liu
2026-09-23 6:02 ` [PATCH v4 02/10] ntfs: validate EA chains and link zero-terminated tails Baolin Liu
2026-09-23 6:02 ` [PATCH v4 03/10] ntfs: propagate EA write and truncate errors Baolin Liu
2026-09-23 6:02 ` [PATCH v4 04/10] ntfs: preserve EA attribute lookup errors Baolin Liu
2026-09-23 6:02 ` [PATCH v4 05/10] ntfs: distinguish empty EA values from removal Baolin Liu
2026-09-23 6:02 ` [PATCH v4 06/10] ntfs: restore EA attributes when an update fails Baolin Liu
2026-09-23 6:02 ` [PATCH v4 07/10] ntfs: add fileattr query support Baolin Liu
2026-09-23 6:02 ` [PATCH v4 08/10] ntfs: persist immutable in the $LINUXFLAGS EA Baolin Liu
2026-09-23 6:02 ` [PATCH v4 09/10] ntfs: persist append-only " Baolin Liu
2026-09-23 6:02 ` [PATCH v4 10/10] ntfs: persist nodump " Baolin Liu
2026-10-12 3:16 ` [PATCH v4 00/10] ntfs: persist Linux file attributes in an EA liubaolin
2026-10-12 4:43 ` Hyunchul Lee [this message]
2026-10-12 5:06 ` Namjae Jeon
2026-10-12 8:15 ` liubaolin
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=asxlX7ysgW7--bE5@hyunchul-PC02 \
--to=hyc.lee@gmail.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=liubaolin@kylinos.cn \
--cc=ntfs@lists.linux.dev \
/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
all inboxes | Powered by JetHome®