From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnd Bergmann <arnd@arndb•de>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Kees Cook <keescook@chromium•org>,
Deepa Dinamani <deepa.kernel@gmail•com>
Subject: linux-next: build warning after merge of the y2038 tree
Date: Wed, 6 Jun 2018 20:41:16 +1000 [thread overview]
Message-ID: <20180606204116.5b01ed36@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2021 bytes --]
Hi all,
After merging the y2038 tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
fs/pstore/ram.c: In function 'ramoops_read_kmsg_hdr':
fs/pstore/ram.c:39:29: warning: format '%ld' expects argument of type 'long int *', but argument 3 has type 'time64_t * {aka long long int *}' [-Wformat=]
#define RAMOOPS_KERNMSG_HDR "===="
^
fs/pstore/ram.c:167:21: note: in expansion of macro 'RAMOOPS_KERNMSG_HDR'
if (sscanf(buffer, RAMOOPS_KERNMSG_HDR TVSEC_FMT ".%lu-%c\n%n",
^~~~~~~~~~~~~~~~~~~
fs/pstore/ram.c:42:23: note: format string is defined here
# define TVSEC_FMT "%ld"
~~^
%lld
fs/pstore/ram.c:39:29: warning: format '%ld' expects argument of type 'long int *', but argument 3 has type 'time64_t * {aka long long int *}' [-Wformat=]
#define RAMOOPS_KERNMSG_HDR "===="
^
fs/pstore/ram.c:174:28: note: in expansion of macro 'RAMOOPS_KERNMSG_HDR'
} else if (sscanf(buffer, RAMOOPS_KERNMSG_HDR TVSEC_FMT ".%lu\n%n",
^~~~~~~~~~~~~~~~~~~
fs/pstore/ram.c:42:23: note: format string is defined here
# define TVSEC_FMT "%ld"
~~^
%lld
fs/pstore/ram.c: In function 'ramoops_write_kmsg_hdr':
fs/pstore/ram.c:39:29: warning: format '%ld' expects argument of type 'long int', but argument 3 has type 'time64_t {aka long long int}' [-Wformat=]
#define RAMOOPS_KERNMSG_HDR "===="
^
fs/pstore/ram.c:370:30: note: in expansion of macro 'RAMOOPS_KERNMSG_HDR'
hdr = kasprintf(GFP_ATOMIC, RAMOOPS_KERNMSG_HDR TVSEC_FMT ".%lu-%c\n",
^~~~~~~~~~~~~~~~~~~
fs/pstore/ram.c:42:23: note: format string is defined here
# define TVSEC_FMT "%ld"
~~^
%lld
Introduced by commit
0f0d83b99ef7 ("pstore: Convert internal records to timespec64")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-06-06 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 10:41 Stephen Rothwell [this message]
2018-06-06 13:47 ` linux-next: build warning after merge of the y2038 tree Arnd Bergmann
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=20180606204116.5b01ed36@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=deepa.kernel@gmail$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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