From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Benson Leung <bleung@google.com>,
Guenter Roeck <groeck@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nick Crews <ncrews@chromium.org>
Subject: Re: linux-next: build warning after merge of the chrome-platform tree
Date: Tue, 16 Apr 2019 11:09:07 +0200 [thread overview]
Message-ID: <3023bc2f-950f-0f78-166a-b54542cc3680@collabora.com> (raw)
In-Reply-To: <20190416143030.07537982@canb.auug.org.au>
On 16/4/19 6:30, Stephen Rothwell wrote:
> Hi all,
>
> After merging the chrome-platform tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/platform/chrome/wilco_ec/debugfs.c:11:
> drivers/platform/chrome/wilco_ec/debugfs.c: In function 'fops_h1_gpio_open':
> drivers/platform/chrome/wilco_ec/debugfs.c:210:59: warning: format '%x' expects argument of type 'unsigned int', but argument 2 has type 'long long unsigned int' [-Wformat=]
> DEFINE_DEBUGFS_ATTRIBUTE(fops_h1_gpio, h1_gpio_get, NULL, "0x%02x\n");
> ^~~~~~~~~~
> include/linux/debugfs.h:45:29: note: in definition of macro 'DEFINE_DEBUGFS_ATTRIBUTE'
> __simple_attr_check_format(__fmt, 0ull); \
> ^~~~~
>
> Introduced by commit
>
> db6c540a0018 ("platform/chrome: wilco_ec: Add h1_gpio status to debugfs")
>
Fixed, I need to automate my builders a bit more to catch these things. Sorry
for the noise. Thanks.
Enric
next prev parent reply other threads:[~2019-04-16 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 4:30 linux-next: build warning after merge of the chrome-platform tree Stephen Rothwell
2019-04-16 9:09 ` Enric Balletbo i Serra [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 5:21 Stephen Rothwell
2021-08-30 7:21 ` Stephen Rothwell
2021-08-31 0:17 ` Benson Leung
2021-08-31 0:32 ` Stephen Rothwell
2022-05-16 11:38 Stephen Rothwell
2022-05-17 13:09 ` Muhammad Usama Anjum
2022-05-18 3:23 ` Bagas Sanjaya
2022-05-18 3:39 ` Tzung-Bi Shih
2022-05-18 4:24 ` Muhammad Usama Anjum
2024-06-03 3:25 Stephen Rothwell
2024-06-03 4:20 ` Tzung-Bi Shih
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=3023bc2f-950f-0f78-166a-b54542cc3680@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ncrews@chromium.org \
--cc=sfr@canb.auug.org.au \
/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