From: Josef Bacik <josef@toxicpanda.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/5] Misc warning fixes
Date: Tue, 18 Aug 2020 11:38:36 -0400 [thread overview]
Message-ID: <1f4f3a04-fb83-ed2e-5b7b-ed8b3cc24880@toxicpanda.com> (raw)
In-Reply-To: <cover.1597666167.git.dsterba@suse.com>
On 8/17/20 8:11 AM, David Sterba wrote:
> Compiling with W=1 or W=2 gives warnings that seem to be worth fixing.
>
> David Sterba (5):
> btrfs: remove const from btrfs_feature_set_name
> btrfs: compression: move declarations to header
> btrfs: remove unnecessarily shadowed variables
> btrfs: scrub: rename ratelimit state varaible to avoid shadowing
> btrfs: send: remove indirect callback parameter for changed_cb
>
> fs/btrfs/backref.c | 1 -
> fs/btrfs/compression.c | 35 -----------------------------------
> fs/btrfs/compression.h | 35 +++++++++++++++++++++++++++++++++++
> fs/btrfs/inode.c | 1 -
> fs/btrfs/scrub.c | 8 ++++----
> fs/btrfs/send.c | 11 ++---------
> fs/btrfs/sysfs.c | 2 +-
> fs/btrfs/sysfs.h | 2 +-
> 8 files changed, 43 insertions(+), 52 deletions(-)
>
The whole series can have
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
prev parent reply other threads:[~2020-08-18 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 12:11 [PATCH 0/5] Misc warning fixes David Sterba
2020-08-17 12:11 ` [PATCH 1/5] btrfs: remove const from btrfs_feature_set_name David Sterba
2020-08-17 12:11 ` [PATCH 2/5] btrfs: compression: move declarations to header David Sterba
2020-08-17 12:11 ` [PATCH 3/5] btrfs: remove unnecessarily shadowed variables David Sterba
2020-08-17 12:11 ` [PATCH 4/5] btrfs: scrub: rename ratelimit state varaible to avoid shadowing David Sterba
2020-08-17 12:11 ` [PATCH 5/5] btrfs: send: remove indirect callback parameter for changed_cb David Sterba
2020-08-18 15:38 ` Josef Bacik [this message]
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=1f4f3a04-fb83-ed2e-5b7b-ed8b3cc24880@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=dsterba@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