From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the qcom tree
Date: Tue, 14 Apr 2020 22:04:20 -0700 [thread overview]
Message-ID: <20200415050420.GA987656@yoga> (raw)
In-Reply-To: <158692631073.105027.12648118734810371009@swboyd.mtv.corp.google.com>
On Tue 14 Apr 21:51 PDT 2020, Stephen Boyd wrote:
> Quoting Stephen Rothwell (2020-04-14 17:25:34)
> > 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")
>
> Thanks. I didn't notice this warning. Looks like we need to cast
> sizeof() to int? Bjorn do you want another patch or does this get
> squashed in?
>
It's in the middle of the patch stack, so I would prefer an additional
patch.
Regards,
Bjorn
> ---8<----
> diff --git a/drivers/soc/qcom/cmd-db.c b/drivers/soc/qcom/cmd-db.c
> index 6c308f92a13c..6b5c440c9dc3 100644
> --- a/drivers/soc/qcom/cmd-db.c
> +++ b/drivers/soc/qcom/cmd-db.c
> @@ -280,7 +280,7 @@ static int cmd_db_debugfs_dump(struct seq_file *seq, void *p)
> ent = rsc_to_entry_header(rsc);
> for (j = 0; j < le16_to_cpu(rsc->cnt); j++, ent++) {
> seq_printf(seq, "0x%08x: %*pEp", le32_to_cpu(ent->addr),
> - sizeof(ent->id), ent->id);
> + (int)sizeof(ent->id), ent->id);
>
> len = le16_to_cpu(ent->len);
> if (len) {
next prev parent reply other threads:[~2020-04-15 5:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 0:25 linux-next: build warning after merge of the qcom tree Stephen Rothwell
2020-04-15 4:51 ` Stephen Boyd
2020-04-15 5:04 ` Bjorn Andersson [this message]
-- 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=20200415050420.GA987656@yoga \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.