From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andy Gross <agross@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Stephen Boyd <swboyd@chromium•org>,
Bjorn Andersson <bjorn.andersson@linaro•org>
Subject: linux-next: build warning after merge of the qcom tree
Date: Wed, 15 Apr 2020 10:25:34 +1000 [thread overview]
Message-ID: <20200415102534.6d22a377@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
Hi all,
After merging the qcom tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/soc/qcom/cmd-db.c: In function 'cmd_db_debugfs_dump':
drivers/soc/qcom/cmd-db.c:281:30: warning: field width specifier '*' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=]
281 | seq_printf(seq, "0x%08x: %*pEp", le32_to_cpu(ent->addr),
| ~^~
| |
| int
282 | sizeof(ent->id), ent->id);
| ~~~~~~~~~~~~~~~
| |
| long unsigned int
Introduced by commit
d6815c5c43d4 ("soc: qcom: cmd-db: Add debugfs dumping file")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-15 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 0:25 Stephen Rothwell [this message]
2020-04-15 4:51 ` linux-next: build warning after merge of the qcom tree Stephen Boyd
2020-04-15 5:04 ` Bjorn Andersson
-- strict thread matches above, loose matches on Subject: below --
2021-10-24 23:28 Stephen Rothwell
2021-10-24 23:40 ` David Heidelberg
2021-10-25 2:24 ` Bjorn Andersson
2019-08-07 0:08 Stephen Rothwell
2018-11-15 23:10 Stephen Rothwell
2018-11-28 21:25 ` Stephen Rothwell
2018-11-29 16:30 ` Stephen Boyd
2018-11-30 4:13 ` Stephen Rothwell
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=20200415102534.6d22a377@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=agross@kernel$(echo .)org \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=swboyd@chromium$(echo .)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