Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs-progs: minor fixes for clang warnings
Date: Fri, 27 Jan 2023 13:41:13 +0800	[thread overview]
Message-ID: <cover.1674797823.git.wqu@suse.com> (raw)

Recently I'm migrating my default compiler from GCC to clang, mostly to
get short comiling time (especially important on my aarch64 machines).

Thus I hit those (mostly false alerts) warnings in btrfs-progs, and come
up with this patchset.

Unfortunately there is still libbtrfsutils causing warnings in
setuptools, as it's still using the default flags from gcc no matter
what.

Qu Wenruo (5):
  btrfs-progs: remove an unnecessary branch to silent the clang warning
  btrfs-progs: fix a false alert on an uninitialized variable when
    BUG_ON() is involved.
  btrfs-progs: fix fallthrough cases with proper attributes
  btrfs-progs: move a union with variable sized type to the end
  btrfs-progs: fix set but not used variables

 cmds/reflink.c              |  2 +-
 cmds/scrub.c                | 12 +++---
 common/format-output.c      |  2 +-
 common/parse-utils.c        | 12 +++---
 common/units.c              |  6 +--
 crypto/xxhash.c             | 73 +++++++++++++++++++------------------
 image/main.c                | 15 +++-----
 kerncompat.h                |  8 ++++
 kernel-shared/ctree.c       | 18 +++++----
 kernel-shared/extent-tree.c |  4 +-
 kernel-shared/print-tree.c  |  2 +-
 kernel-shared/volumes.c     |  3 +-
 kernel-shared/zoned.c       |  6 +--
 mkfs/main.c                 |  4 --
 14 files changed, 84 insertions(+), 83 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-01-27  5:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  5:41 Qu Wenruo [this message]
2023-01-27  5:41 ` [PATCH 1/5] btrfs-progs: remove an unnecessary branch to silent the clang warning Qu Wenruo
2023-01-27  5:41 ` [PATCH 2/5] btrfs-progs: fix a false alert on an uninitialized variable when BUG_ON() is involved Qu Wenruo
2023-01-27  5:41 ` [PATCH 3/5] btrfs-progs: fix fallthrough cases with proper attributes Qu Wenruo
2023-02-09 19:24   ` David Sterba
2023-01-27  5:41 ` [PATCH 4/5] btrfs-progs: move a union with variable sized type to the end Qu Wenruo
2023-01-27  5:41 ` [PATCH 5/5] btrfs-progs: fix set but not used variables Qu Wenruo
2023-01-30  7:28 ` [PATCH 0/5] btrfs-progs: minor fixes for clang warnings Qu Wenruo
2023-01-30  8:14   ` hmsjwzb
2023-02-09 19:26 ` 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=cover.1674797823.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