From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>, Liam Girdwood <lgirdwood@gmail•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Matti Vaittinen <matti.vaittinen@fi•rohmeurope.com>
Subject: linux-next: build warning after merge of the regulator tree
Date: Tue, 2 Oct 2018 13:07:48 +1000 [thread overview]
Message-ID: <20181002130748.61e33ad1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
Hi all,
After merging the regulator tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/mfd/rohm-bd718x7.c: In function 'bd718xx_i2c_probe':
drivers/mfd/rohm-bd718x7.c:101:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
bd718xx->chip_type = (unsigned int)
^
Introduced by commit
494edd266b94 ("regulator/mfd: Support ROHM BD71847 power management IC")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-10-02 3:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 3:07 Stephen Rothwell [this message]
2018-10-02 6:16 ` linux-next: build warning after merge of the regulator tree Matti Vaittinen
2018-10-02 6:25 ` Stephen Rothwell
2018-10-02 6:43 ` Matti Vaittinen
2018-10-02 13:02 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 4:52 Stephen Rothwell
2024-10-23 4:51 Stephen Rothwell
2020-01-10 2:41 Stephen Rothwell
2016-04-18 3:43 Stephen Rothwell
2016-04-18 9:15 ` Mark Brown
2015-10-07 2:45 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=20181002130748.61e33ad1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=matti.vaittinen@fi$(echo .)rohmeurope.com \
/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