Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/6] btrfs-progs: remove unused header for tune/main.c
Date: Tue, 2 Apr 2024 20:42:16 +0200	[thread overview]
Message-ID: <20240402184216.GE14596@twin.jikos.cz> (raw)
In-Reply-To: <a7224b1e785d51d74c6bd369ee0c0f586cbdf616.1711412540.git.wqu@suse.com>

On Tue, Mar 26, 2024 at 10:52:41AM +1030, Qu Wenruo wrote:
> My clangd LSP server reports warning that "common/parse-utils.h" is not
> utilized at all.

Please be careful about removing headers, the LSP depends on the
build flags and reports symbols or headers only for the last configured
state.

In this case removing parse-utils.h causes compilation error in
experimental mode because of

287 #if EXPERIMENTAL
288                 case GETOPT_VAL_CSUM:
289                         btrfs_warn_experimental(
290                                 "Switching checksums is experimental, do not use for valuable data!");
291                         ctree_flags |= OPEN_CTREE_SKIP_CSUM_CHECK;
292                         csum_type = parse_csum_type(optarg);
                                        ^^^^^^^^^^^^^^^^^^^^^^^

293                         btrfstune_cmd_groups[CSUM_CHANGE] = true;
294                         break;
295 #endif

Some build checks or targets could be missing so we'd lack coverage and
early warnings during development, this needs to be fixed.

Builds that change LSP state (and combinations):

- make box
- make static box.static
- various D= values and modes
- configure --experimental
- possibly different includes for glibc and musl defining a symbol
  indirectly

  reply	other threads:[~2024-04-02 18:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-26  0:22 [PATCH 0/6] btrfs-progs: zoned devices support for bgt feature Qu Wenruo
2024-03-26  0:22 ` [PATCH 1/6] btrfs-progs: remove unused header for tune/main.c Qu Wenruo
2024-04-02 18:42   ` David Sterba [this message]
2024-04-02 21:30     ` Qu Wenruo
2024-03-26  0:22 ` [PATCH 2/6] btrfs-progs: tune: add the missing newline for --convert-from-block-group-tree Qu Wenruo
2024-03-26  0:22 ` [PATCH 3/6] btrfs-progs: mkfs: use proper zoned compatible write for bgt feature Qu Wenruo
2024-03-26  0:22 ` [PATCH 4/6] btrfs-progs: tune: properly open zoned devices for RW Qu Wenruo
2024-03-26  0:22 ` [PATCH 5/6] btrfs-progs: tests-mkfs: add test case for zoned block group tree feature Qu Wenruo
2024-03-26  0:22 ` [PATCH 6/6] btrfs-progs: tests-misc: add a test case to check zoned bgt conversion Qu Wenruo
2024-03-26 16:53 ` [PATCH 0/6] btrfs-progs: zoned devices support for bgt feature Johannes Thumshirn
2024-03-27  1:23 ` Naohiro Aota
2024-03-27 23:52 ` David Sterba

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=20240402184216.GE14596@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.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