From: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
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 regulator tree
Date: Tue, 2 Oct 2018 09:16:44 +0300 [thread overview]
Message-ID: <20181002061644.GC9389@localhost.localdomain> (raw)
In-Reply-To: <20181002130748.61e33ad1@canb.auug.org.au>
Hello All,
On Tue, Oct 02, 2018 at 01:07:48PM +1000, Stephen Rothwell wrote:
> 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)
I am pretty sure the last patch version corrected this to
+ bd71837->chip_type = (unsigned int)(uintptr_t)
+ of_device_get_match_data(&i2c->dev);
is it possible one of the earlier versions has accidentally been
applied? Should I create patch on top of the last regulator tree or what
is the simplest way fix this?
Br,
Matti Vaittinen
next prev parent reply other threads:[~2018-10-02 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 3:07 linux-next: build warning after merge of the regulator tree Stephen Rothwell
2018-10-02 6:16 ` Matti Vaittinen [this message]
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=20181002061644.GC9389@localhost.localdomain \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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 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.