From: Gabriel Shahrouzi <gshahrouzi@gmail.com>
To: kent.overstreet@linux.dev
Cc: gshahrouzi@gmail.com, linux-bcachefs@vger.kernel.org,
shuah@kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: [PATCH 0/3] This series addresses several minor issues found using sparse.
Date: Thu, 3 Apr 2025 21:28:19 -0400 [thread overview]
Message-ID: <20250404012822.188485-1-gshahrouzi@gmail.com> (raw)
The first patch fixes a typo ('\%u') in a format specifier within a print
statement. The incorrect sequence was replaced as it didn't appear
to be the author's intent.
The second patch corrects the type for a function argument to __le64,
which fixes two related sparse warnings. Although the argument data
is already little-endian, using the specific __le64 type improves
consistency and makes the expected data format explicit.
The third patch ensures cpu_to_le16() is used when preparing certain
on-disk data (directory entry lengths). This maintains correct byte
ordering for big-endian systems.
Gabriel Shahrouzi (3):
bcachefs: Fix escape sequence in prt_printf
bcachefs: Fix type for parameter in
journal_advance_devs_to_next_bucket
bcachefs: Use cpu_to_le16 for dirent lengths
fs/bcachefs/data_update.c | 2 +-
fs/bcachefs/dirent.c | 4 ++--
fs/bcachefs/journal_io.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-04 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 1:28 Gabriel Shahrouzi [this message]
2025-04-04 1:28 ` [PATCH 1/3] bcachefs: Fix escape sequence in prt_printf Gabriel Shahrouzi
2025-04-04 1:28 ` [PATCH 2/3] bcachefs: Fix type for parameter in journal_advance_devs_to_next_bucket Gabriel Shahrouzi
2025-04-04 1:28 ` [PATCH 3/3] bcachefs: Use cpu_to_le16 for dirent lengths Gabriel Shahrouzi
2025-04-04 1:34 ` [PATCH 0/3] This series addresses several minor issues found using sparse Kent Overstreet
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=20250404012822.188485-1-gshahrouzi@gmail.com \
--to=gshahrouzi@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@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