From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: osandov@osandov.com
Subject: [PATCH 0/4] btrfs-progs: Compiling warning fixes for devel branch
Date: Mon, 18 Nov 2019 14:30:48 +0800 [thread overview]
Message-ID: <20191118063052.56970-1-wqu@suse.com> (raw)
We have several compiling errors, in devel branch.
One looks like a false alert from compiler, the first patch will
workaround it.
3 warning from libbtrfsutils are due to python3.8 changes.
Handle it properly by using designated initialization, which also saves
us quite some lines.
Qu Wenruo (4):
btrfs-progs: check/lowmem: Fix a false alert on uninitialized value
btrfs-progs: libbtrfsutil: Convert to designated initialization for
BtrfsUtilError_type
btrfs-progs: libbtrfsutil: Convert to designated initialization for
QgroupInherit_type
btrfs-progs: libbtrfsutil: Convert to designated initialization for
SubvolumeIterator_type
check/mode-common.c | 2 +-
libbtrfsutil/python/error.c | 49 ++++++++-------------------------
libbtrfsutil/python/qgroup.c | 43 ++++++-----------------------
libbtrfsutil/python/subvolume.c | 44 ++++++-----------------------
4 files changed, 30 insertions(+), 108 deletions(-)
--
2.24.0
next reply other threads:[~2019-11-18 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 6:30 Qu Wenruo [this message]
2019-11-18 6:30 ` [PATCH 1/4] btrfs-progs: check/lowmem: Fix a false alert on uninitialized value Qu Wenruo
2019-11-18 6:30 ` [PATCH 2/4] btrfs-progs: libbtrfsutil: Convert to designated initialization for BtrfsUtilError_type Qu Wenruo
2019-11-18 6:30 ` [PATCH 3/4] btrfs-progs: libbtrfsutil: Convert to designated initialization for QgroupInherit_type Qu Wenruo
2019-11-18 6:30 ` [PATCH 4/4] btrfs-progs: libbtrfsutil: Convert to designated initialization for SubvolumeIterator_type Qu Wenruo
2019-11-18 8:23 ` [PATCH 0/4] btrfs-progs: Compiling warning fixes for devel branch Nikolay Borisov
2019-11-18 18:10 ` David Sterba
2019-11-18 18:27 ` Omar Sandoval
2019-11-18 23:47 ` Qu WenRuo
2019-11-19 20:38 ` Omar Sandoval
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=20191118063052.56970-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).