From: Chi Zhiling <chizhiling@163.com>
To: "Yuezhang.Mo@sony.com" <Yuezhang.Mo@sony.com>
Cc: "brauner@kernel.org" <brauner@kernel.org>,
"chizhiling@kylinos.cn" <chizhiling@kylinos.cn>,
"jack@suse.cz" <jack@suse.cz>,
"linkinjeon@kernel.org" <linkinjeon@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sj1557.seo@samsung.com" <sj1557.seo@samsung.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"willy@infradead.org" <willy@infradead.org>
Subject: Re: [PATCH v1 8/9] exfat: support multi-cluster for exfat_map_cluster
Date: Wed, 31 Dec 2025 09:51:30 +0800 [thread overview]
Message-ID: <49331fb0-9cfe-4ec9-a819-60ab62de15e7@163.com> (raw)
In-Reply-To: <PUZPR04MB6316AEB35F215CCA9BB0895181BCA@PUZPR04MB6316.apcprd04.prod.outlook.com>
On 12/30/25 17:06, Yuezhang.Mo@sony.com wrote:
>> @@ -293,12 +298,14 @@ static int exfat_get_block(struct inode *inode, sector_t iblock,
>>
>> if (cluster == EXFAT_EOF_CLUSTER)
>> goto done;
>> + if (WARN_ON_ONCE(!count))
>> + count = 1;
>
> The count is 0 only if cluster is EXFAT_EOF_CLUSTER.
> So this warning never occur, right? If yes, please remove it.
Yes, it's never 0 unless something goes wrong :)
I will remove it in v2.
next prev parent reply other threads:[~2025-12-31 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 9:06 Yuezhang.Mo
2025-12-31 1:51 ` Chi Zhiling [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-26 9:44 [PATCH v1 0/9] Enable exfat_get_block to support obtaining multiple clusters Chi Zhiling
2025-12-26 9:44 ` [PATCH v1 8/9] exfat: support multi-cluster for exfat_map_cluster Chi Zhiling
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=49331fb0-9cfe-4ec9-a819-60ab62de15e7@163.com \
--to=chizhiling@163.com \
--cc=Yuezhang.Mo@sony.com \
--cc=brauner@kernel.org \
--cc=chizhiling@kylinos.cn \
--cc=jack@suse.cz \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®