From: Senjin <senjin@hatchling.org>
To: ntfs3@lists.linux.dev
Cc: almaz.alexandrovich@paragon-software.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
Date: 29 Jun 2026 08:19:22 -0000 [thread overview]
Message-ID: <6a422a8ad00bb927e47582d0@mailersend.net> (raw)
In-Reply-To: <20260613201610.14467-2-senjin@hatchling.org>
Gentle ping on this two-patch series (v2, sent 2026-06-13). Any feedback welcome.
--
Senjin
prev parent reply other threads:[~2026-06-29 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260613201610.14467-1-senjin@hatchling.org>
2026-06-13 20:16 ` Senjin
2026-06-13 20:16 ` [PATCH v2 2/2] fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters Senjin
[not found] ` <20260613201610.14467-2-senjin@hatchling.org>
2026-06-29 8:19 ` Senjin [this message]
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=6a422a8ad00bb927e47582d0@mailersend.net \
--to=senjin@hatchling.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@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