From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org
Subject: [PATCH 0/4] e2fsprogs: a few more warning fixes
Date: Sat, 28 Jan 2023 14:46:47 -0800 [thread overview]
Message-ID: <20230128224651.59593-1-ebiggers@kernel.org> (raw)
Fix the GitHub Actions workflow to really use -Werror when building the
libraries, fix a recently introduced warning in debugfs, and fix two
warnings in the Windows build.
Eric Biggers (4):
ci.yml: ensure -Werror really gets used in all cases
debugfs: fix a -Wformat warning in dump_journal()
lib/ext2fs: don't warn about lack of getmntent on Windows
lib/uuid: remove unneeded Windows UUID workaround
.github/workflows/ci.yml | 28 ++++++++++++++--------------
debugfs/logdump.c | 3 ++-
lib/ext2fs/Android.bp | 1 -
lib/ext2fs/ismounted.c | 2 +-
lib/uuid/Android.bp | 2 --
lib/uuid/gen_uuid.c | 5 -----
lib/uuid/tst_uuid.c | 6 ------
lib/uuid/uuid_time.c | 6 ------
8 files changed, 17 insertions(+), 36 deletions(-)
base-commit: 0352d353adbe6c5d6f1937e12c66e599b8657d72
--
2.39.1
next reply other threads:[~2023-01-28 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 22:46 Eric Biggers [this message]
2023-01-28 22:46 ` [PATCH 1/4] ci.yml: ensure -Werror really gets used in all cases Eric Biggers
2023-01-30 5:07 ` Theodore Ts'o
2023-01-28 22:46 ` [PATCH 2/4] debugfs: fix a -Wformat warning in dump_journal() Eric Biggers
2023-01-30 5:08 ` Theodore Ts'o
2023-01-28 22:46 ` [PATCH 3/4] lib/ext2fs: don't warn about lack of getmntent on Windows Eric Biggers
2023-01-30 5:08 ` Theodore Ts'o
2023-01-28 22:46 ` [PATCH 4/4] lib/uuid: remove unneeded Windows UUID workaround Eric Biggers
2023-01-30 5:09 ` Theodore Ts'o
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=20230128224651.59593-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).