[PATCH] Fix 0x%u usage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



There's a couple of places which use varients on "0x%u" in
format strings; that's almost always wrong - you either want
0x%x or just %u.
In libmount's case it's flags, so I'm assuming the intention
really is hex.
In the ja.po case it's %u in the original msgid.

Signed-off-by: Dr. David Alan Gilbert <dave@xxxxxxxxxxx>
---
 libmount/src/optstr.c | 2 +-
 po/ja.po              | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/libmount/src/optstr.c b/libmount/src/optstr.c
index 9af594f52..68b7bc383 100644
--- a/libmount/src/optstr.c
+++ b/libmount/src/optstr.c
@@ -731,7 +731,7 @@ int mnt_optstr_apply_flags(char **optstr, unsigned long flags,
 	if (!optstr || !map)
 		return -EINVAL;
 
-	DBG(CXT, ul_debug("applying 0x%08lu flags to '%s'", flags, *optstr));
+	DBG(CXT, ul_debug("applying 0x%08lx flags to '%s'", flags, *optstr));
 
 	maps[0] = map;
 	next = *optstr;
diff --git a/po/ja.po b/po/ja.po
index ec2c550ec..4974c0bcc 100644
--- a/po/ja.po
+++ b/po/ja.po
@@ -6820,7 +6820,7 @@ msgstr "間違った vtoc.sanity 値 [0x%08x] の sun ディスクラベルを
 #: libfdisk/src/sun.c:163
 #, c-format
 msgid "Detected sun disklabel with wrong vtoc.nparts [%u]."
-msgstr "間違った vtoc.nparts 値 [0x%u] の sun ディスクラベルを検出しました。"
+msgstr "間違った vtoc.nparts 値 [%u] の sun ディスクラベルを検出しました。"
 
 #: libfdisk/src/sun.c:168
 msgid "Warning: Wrong values need to be fixed up and will be corrected by w(rite)"
-- 
2.28.0




[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux