public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Kangjie Lu <kjlu@umn•edu>
Subject: Re: linux-next: build warning after merge of the leds tree
Date: Tue, 19 Mar 2019 20:53:40 +0100	[thread overview]
Message-ID: <33578161-eed4-3f19-5fcb-09e4b400dd18@gmail.com> (raw)
In-Reply-To: <20190319135833.64ad30b8@canb.auug.org.au>

Hi Stephen,

Thank you for the report.

On 3/19/19 3:58 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the leds tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
> 
> drivers/leds/leds-pca9532.c: In function 'pca9532_probe':
> drivers/leds/leds-pca9532.c:536:11: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>     devid = (int)of_id->data;
>             ^

Applied the fixup to the original commit, which missed to carry
the cast properly from the previous state of code.

-               devid = (int)of_id->data;
+               devid = (int)(uintptr_t) of_id->data;


> Introduced by commit
> 
>    6b788fae618c ("leds: fix a potential NULL pointer dereference")
> 

-- 
Best regards,
Jacek Anaszewski

  reply	other threads:[~2019-03-19 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  2:58 linux-next: build warning after merge of the leds tree Stephen Rothwell
2019-03-19 19:53 ` Jacek Anaszewski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-14  3:46 Stephen Rothwell
2019-02-14  7:51 ` Michal Kazior
2019-02-14 21:13 ` Jacek Anaszewski

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=33578161-eed4-3f19-5fcb-09e4b400dd18@gmail.com \
    --to=jacek.anaszewski@gmail$(echo .)com \
    --cc=kjlu@umn$(echo .)edu \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /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