From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org
Cc: Daniel Kiper <dkiper@net-space.pl>,
Glenn Washburn <development@efficientek.com>
Subject: [PATCH v2 0/2] error: Do compile-time format string checking on grub_error.
Date: Sat, 7 Nov 2020 23:26:17 -0600 [thread overview]
Message-ID: <cover.1604812408.git.development@efficientek.com> (raw)
In-Reply-To: <20201005061739.640766-1-development@efficientek.com>
I've separated this into two patches from the previous one, but nothing else
has changed (except the commit message). I think at least the first patch should
be applied. Since I don't have a setup to test every architecture+platform
build of grub, I can't gaurantee that the second patch won't cause a build error
on some other architecture+platform combo. However, if it does, I'll bet it'll
get fixed quickly. However, for that reason, I suggest the second patch be
applied after the 2.06 release (might be moot at this point). This series has
successfully built for me for i386-pc and x86_64-efi.
Glenn
Glenn Washburn (2):
error: Fix issues mostly related to incorrect length modifiers in
calls to grub_error().
error: Do compile-time format string checking on grub_error.
grub-core/commands/pgp.c | 2 +-
grub-core/disk/ata.c | 4 ++--
grub-core/disk/cryptodisk.c | 14 ++++++++------
grub-core/disk/dmraid_nvidia.c | 2 +-
grub-core/disk/luks2.c | 6 +++---
grub-core/efiemu/i386/loadcore64.c | 3 ++-
grub-core/fs/hfsplus.c | 3 ++-
grub-core/fs/zfs/zfs.c | 2 +-
grub-core/kern/efi/efi.c | 2 +-
grub-core/kern/efi/mm.c | 2 +-
grub-core/kern/x86_64/dl.c | 2 +-
grub-core/loader/efi/chainloader.c | 4 ++--
grub-core/loader/i386/bsd.c | 3 ++-
grub-core/loader/i386/pc/linux.c | 4 ++--
grub-core/net/tftp.c | 2 +-
grub-core/parttool/msdospart.c | 4 ++--
grub-core/script/lexer.c | 2 +-
grub-core/video/bochs.c | 4 ++--
include/grub/err.h | 3 ++-
19 files changed, 37 insertions(+), 31 deletions(-)
--
2.27.0
next prev parent reply other threads:[~2020-11-08 5:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 14:33 [PATCH] error: Do compile-time format string checking on grub_error Glenn Washburn
2020-07-31 14:33 ` [PATCH] cryptodisk: Use cipher name instead of object in error message Glenn Washburn
2020-09-17 14:30 ` Daniel Kiper
2020-07-31 14:33 ` [PATCH] lexer: char const * should be const char * Glenn Washburn
2020-09-17 14:33 ` Daniel Kiper
2020-07-31 14:33 ` [PATCH] docs/grub: Support for loading and concatenating multiple initrds Glenn Washburn
2020-09-17 14:36 ` Daniel Kiper
2020-07-31 14:33 ` [PATCH] script: Do not allow a delimiter between function name and block start Glenn Washburn
2020-09-17 14:40 ` Daniel Kiper
2020-07-31 14:33 ` [PATCH] crypto: Remove GPG_ERROR_CFLAGS from gpg_err_code_t enum Glenn Washburn
2020-09-17 14:42 ` Daniel Kiper
2020-09-17 14:29 ` [PATCH] error: Do compile-time format string checking on grub_error Daniel Kiper
2020-10-03 22:34 ` Glenn Washburn
2020-10-05 6:12 ` Glenn Washburn
2020-10-05 6:17 ` Glenn Washburn
2020-11-08 5:26 ` Glenn Washburn [this message]
2020-11-08 5:26 ` [PATCH v2 1/2] error: Fix issues mostly related to incorrect length modifiers in calls to grub_error() Glenn Washburn
2020-11-08 5:26 ` [PATCH v2 2/2] error: Do compile-time format string checking on grub_error Glenn Washburn
2020-11-23 9:31 ` [PATCH v2 0/2] " Glenn Washburn
2020-12-01 5:59 ` Glenn Washburn
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.1604812408.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.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