From: Kishon Vijay Abraham I <kishon@ti•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Greg KH <greg@kroah•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
John Crispin <john@phrozen•org>,
Harvey Hunt <harvey.hunt@imgtec•com>
Subject: Re: linux-next: build warning after merge of the phy-next tree
Date: Thu, 24 Aug 2017 13:31:43 +0530 [thread overview]
Message-ID: <a5d1d4a4-e19f-d92b-f985-81683a933933@ti.com> (raw)
In-Reply-To: <20170824152335.7d9977e8@canb.auug.org.au>
Stephen,
On Thursday 24 August 2017 10:53 AM, Stephen Rothwell wrote:
> Hi Greg,
>
> On Tue, 22 Aug 2017 15:07:33 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>>
>> Hi Kishon,
>>
>> After merging the phy-next tree, today's linux-next build (x86_64
>> allmodconfig) produced this warning:
>>
>> drivers/phy/ralink/phy-ralink-usb.c: In function 'ralink_usb_phy_probe':
>> drivers/phy/ralink/phy-ralink-usb.c:195:13: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>> phy->clk = (u32) match->data;
>> ^
>>
>> Introduced by commit
>>
>> 2411a736ff09 ("phy: ralink-usb: add driver for Mediatek/Ralink")
>
> I now get this warning after merging the usb tree ...
I've now sent a patch from Arnd to fix it.
Thanks
Kishon
next prev parent reply other threads:[~2017-08-24 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 5:07 linux-next: build warning after merge of the phy-next tree Stephen Rothwell
2017-08-24 5:23 ` Stephen Rothwell
2017-08-24 8:01 ` Kishon Vijay Abraham I [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 5:17 Stephen Rothwell
2020-01-07 5:26 ` Ramuthevar, Vadivel MuruganX
2019-03-28 0:29 Stephen Rothwell
2019-03-28 3:03 ` Srinath Mannam
2016-11-16 3:00 Stephen Rothwell
2016-11-16 13:28 ` wlf
2016-11-16 16:39 ` Kishon Vijay Abraham I
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=a5d1d4a4-e19f-d92b-f985-81683a933933@ti.com \
--to=kishon@ti$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=harvey.hunt@imgtec$(echo .)com \
--cc=john@phrozen$(echo .)org \
--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