From: Leon Romanovsky <leon@kernel.org>
To: Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Fixes to GCC warnings while compiling with W=1 level
Date: Wed, 19 Aug 2020 17:21:29 +0300 [thread overview]
Message-ID: <20200819142129.GW7555@unreal> (raw)
In-Reply-To: <20200819141630.1338693-1-leon@kernel.org>
On Wed, Aug 19, 2020 at 05:16:27PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> The series of trivial fixes for GCC warnings seen while compiling with W=1.
>
> Thanks
>
> Leon Romanovsky (3):
> fs/btfrs: Fix -Wunused-but-set-variable warnings
^^^ this is typo - btrfs
> fs/btrfs: Fix -Wignored-qualifiers warnings
> fs/btrfs: Fix -Wmissing-prototypes warnings
>
> fs/btrfs/compression.c | 35 -----------------------------------
> fs/btrfs/compression.h | 35 +++++++++++++++++++++++++++++++++++
> fs/btrfs/ctree.c | 2 +-
> fs/btrfs/ctree.h | 2 +-
> fs/btrfs/sysfs.c | 7 +++----
> fs/btrfs/sysfs.h | 2 +-
> 6 files changed, 41 insertions(+), 42 deletions(-)
>
> --
> 2.26.2
>
next prev parent reply other threads:[~2020-08-19 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 14:16 [PATCH 0/3] Fixes to GCC warnings while compiling with W=1 level Leon Romanovsky
2020-08-19 14:16 ` [PATCH 1/3] fs/btfrs: Fix -Wunused-but-set-variable warnings Leon Romanovsky
2020-08-19 14:16 ` [PATCH 2/3] fs/btrfs: Fix -Wignored-qualifiers warnings Leon Romanovsky
2020-08-19 14:16 ` [PATCH 3/3] fs/btrfs: Fix -Wmissing-prototypes warnings Leon Romanovsky
2020-08-19 14:21 ` Leon Romanovsky [this message]
2020-08-19 15:39 ` [PATCH 0/3] Fixes to GCC warnings while compiling with W=1 level 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=20200819142129.GW7555@unreal \
--to=leon@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.