From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: simple cleanup related to LLVM (not LLM)
Date: Tue, 27 Oct 2026 19:05:30 +1030 [thread overview]
Message-ID: <cover.1793090084.git.wqu@suse.com> (raw)
When using LLVM to compile btrfs-progs, two unused global variables are exposed.
Fix them.
Secondly recently I move to use `GNUmakefile` to customize the make behavior,
e.g. add "-j12" make flags, without modifying the existing Makefile.
Also add GNUmakefile to gitignore.
Qu Wenruo (2):
btrfs-progs: remove set but unused variables
btrfs-progs: gitignore: add GNUmakefile
GNUmakefile | 2 ++
cmds/inspect-tree-stats.c | 3 ---
cmds/rescue-fix-data-checksum.c | 2 --
3 files changed, 2 insertions(+), 5 deletions(-)
create mode 100644 GNUmakefile
--
2.56.0
next reply other threads:[~2026-10-27 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:35 Qu Wenruo [this message]
2026-10-27 8:35 ` [PATCH 1/2] btrfs-progs: remove set but unused variables Qu Wenruo
2026-10-27 9:18 ` Daniel Vacek
2026-10-27 8:35 ` [PATCH 2/2] btrfs-progs: gitignore: add GNUmakefile Qu Wenruo
2026-10-27 9:16 ` Daniel Vacek
2026-10-27 9:29 ` Qu Wenruo
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=cover.1793090084.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.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