From: William Hansen-Baird <william.hansen.baird@gmail.com>
To: linkinjeon@kernel.org, sj1557.seo@samsung.com
Cc: yuezhang.mo@sony.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
William Hansen-Baird <william.hansen.baird@gmail.com>
Subject: [PATCH 2/2] exfat: add blank line after declarations
Date: Wed, 21 Jan 2026 19:04:34 -0500 [thread overview]
Message-ID: <20260122000451.160907-2-william.hansen.baird@gmail.com> (raw)
In-Reply-To: <20260122000451.160907-1-william.hansen.baird@gmail.com>
Add a blank line after variable declarations in fatent.c and file.c.
This improves readability and makes code style more consistent
across the exfat subsystem.
Signed-off-by: William Hansen-Baird <william.hansen.baird@gmail.com>
---
fs/exfat/fatent.c | 1 +
fs/exfat/file.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/fs/exfat/fatent.c b/fs/exfat/fatent.c
index c9c5f2e3a05e..543ce7e8d367 100644
--- a/fs/exfat/fatent.c
+++ b/fs/exfat/fatent.c
@@ -192,6 +192,7 @@ static int __exfat_free_cluster(struct inode *inode, struct exfat_chain *p_chain
if (p_chain->flags == ALLOC_NO_FAT_CHAIN) {
int err;
unsigned int last_cluster = p_chain->dir + p_chain->size - 1;
+
do {
bool sync = false;
diff --git a/fs/exfat/file.c b/fs/exfat/file.c
index 536c8078f0c1..c7cfa28a3e11 100644
--- a/fs/exfat/file.c
+++ b/fs/exfat/file.c
@@ -682,6 +682,7 @@ static ssize_t exfat_file_write_iter(struct kiocb *iocb, struct iov_iter *iter)
if (iocb->ki_pos > pos) {
ssize_t err = generic_write_sync(iocb, iocb->ki_pos - pos);
+
if (err < 0)
return err;
}
--
2.52.0
next prev parent reply other threads:[~2026-01-22 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 0:04 [PATCH 1/2] exfat: remove unnecessary else after return statement William Hansen-Baird
2026-01-22 0:04 ` William Hansen-Baird [this message]
2026-01-22 11:52 ` [PATCH 2/2] exfat: add blank line after declarations Namjae Jeon
2026-01-22 11:52 ` [PATCH 1/2] exfat: remove unnecessary else after return statement Namjae Jeon
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=20260122000451.160907-2-william.hansen.baird@gmail.com \
--to=william.hansen.baird@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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 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®