From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: CIFS <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Linux-Next Mailing List"
<linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Linux Kernel Mailing List"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
Subject: Re: linux-next: build warning after merge of the cifs tree
Date: Mon, 26 Jun 2017 11:57:46 -0500 [thread overview]
Message-ID: <CAH2r5mstCdHYdaJ1kQEDO5SiJP1gDNTQiXqZ3s3mW==XfCx7mw@mail.gmail.com> (raw)
In-Reply-To: <20170626100728.0494601c-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
I just merged an updated version of this patch to remove the warning
to cifs-2.6.git for-next
On Sun, Jun 25, 2017 at 7:07 PM, Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org> wrote:
> Hi all,
>
> After merging the cifs tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/kernel.h:13:0,
> from include/linux/list.h:8,
> from include/linux/wait.h:6,
> from include/linux/fs.h:5,
> from fs/cifs/smb2transport.c:25:
> fs/cifs/smb2transport.c: In function 'generate_smb3signingkey':
> fs/cifs/cifs_debug.h:55:24: warning: field width specifier '*' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=]
> pr_debug_ratelimited("%s: " \
> ^
> include/linux/printk.h:285:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^
> fs/cifs/cifs_debug.h:55:3: note: in expansion of macro 'pr_debug_ratelimited'
> pr_debug_ratelimited("%s: " \
> ^
> fs/cifs/smb2transport.c:352:2: note: in expansion of macro 'cifs_dbg'
> cifs_dbg(VFS, "Session Id %*ph\n", sizeof(ses->Suid), &ses->Suid);
> ^
> In file included from fs/cifs/smb2transport.c:39:0:
> fs/cifs/smb2transport.c:352:16: warning: field width specifier '*' expects argument of type 'int', but argument 2 has type 'long unsigned int' [-Wformat=]
> cifs_dbg(VFS, "Session Id %*ph\n", sizeof(ses->Suid), &ses->Suid);
> ^
> fs/cifs/cifs_debug.h:58:16: note: in definition of macro 'cifs_dbg'
> cifs_vfs_err(fmt, ##__VA_ARGS__); \
> ^
> In file included from include/linux/kernel.h:13:0,
> from include/linux/list.h:8,
> from include/linux/wait.h:6,
> from include/linux/fs.h:5,
> from fs/cifs/smb2transport.c:25:
> fs/cifs/smb2transport.c:352:16: warning: field width specifier '*' expects argument of type 'int', but argument 3 has type 'long unsigned int' [-Wformat=]
> cifs_dbg(VFS, "Session Id %*ph\n", sizeof(ses->Suid), &ses->Suid);
> ^
> include/linux/printk.h:285:21: note: in definition of macro 'pr_fmt'
> #define pr_fmt(fmt) fmt
> ^
> fs/cifs/cifs_debug.h:60:3: note: in expansion of macro 'pr_debug_ratelimited'
> pr_debug_ratelimited(fmt, ##__VA_ARGS__); \
> ^
> fs/cifs/smb2transport.c:352:2: note: in expansion of macro 'cifs_dbg'
> cifs_dbg(VFS, "Session Id %*ph\n", sizeof(ses->Suid), &ses->Suid);
> ^
>
> Introduced by commit
>
> ba4f2a8b205f ("CIFS: add CONFIG_CIFS_DEBUG_KEYS to dump encryption keys")
>
> --
> Cheers,
> Stephen Rothwell
--
Thanks,
Steve
next prev parent reply other threads:[~2017-06-26 16:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 0:07 linux-next: build warning after merge of the cifs tree Stephen Rothwell
[not found] ` <20170626100728.0494601c-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-06-26 16:57 ` Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 1:47 Stephen Rothwell
2024-01-19 3:02 ` Steve French
2022-05-23 0:57 Stephen Rothwell
2022-05-23 2:29 ` Steve French
2021-02-04 22:51 Stephen Rothwell
2019-07-18 23:16 Stephen Rothwell
2019-07-18 23:38 ` Steve French
2018-01-03 22:33 Stephen Rothwell
2018-01-03 22:44 ` Steve French
[not found] ` <CAH2r5mvgtC3Y_aLxk7-_R8E=ohR1LoFSkiqZZ6rhn9azXY05xw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-04 5:52 ` Stephen Rothwell
2017-11-20 23:19 Stephen Rothwell
[not found] ` <20171121101916.4970d5f9-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2017-11-20 23:37 ` Steve French
2011-01-31 2:30 Stephen Rothwell
2011-01-31 10:49 ` Suresh Jayaraman
[not found] ` <4D4693CF.9090903-l3A5Bk7waGM@public.gmane.org>
2011-01-31 11:38 ` Pavel Shilovsky
2011-01-31 12:29 ` Jeff Layton
2011-01-31 2:27 Stephen Rothwell
[not found] ` <20110131132743.4ae5d4ae.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2011-01-31 3:25 ` Steve French
2011-01-31 2:25 Stephen Rothwell
2011-01-21 1:05 Stephen Rothwell
2011-01-21 1:20 ` Jeff Layton
2010-09-24 3:55 Stephen Rothwell
[not found] ` <20100924135531.96e5ac72.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-10-19 5:21 ` Stephen Rothwell
2010-10-19 13:13 ` Jeff Layton
[not found] ` <20101019091339.38e45faa-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-10-19 15:48 ` Shirish Pargaonkar
2010-09-24 3:48 Stephen Rothwell
2010-09-24 11:13 ` Jeff Layton
2010-08-26 1:02 Stephen Rothwell
[not found] ` <20100826110229.931ab5bf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2010-08-26 2:07 ` Steve French
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='CAH2r5mstCdHYdaJ1kQEDO5SiJP1gDNTQiXqZ3s3mW==XfCx7mw@mail.gmail.com' \
--to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aaptel-IBi9RG/b67k@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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).