From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, John Crispin <john@phrozen.org>,
Harvey Hunt <harvey.hunt@imgtec.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: ralink: fix 64-bit build warning
Date: Wed, 23 Aug 2017 16:30:23 -0700 [thread overview]
Message-ID: <20170823233023.GA7482@kroah.com> (raw)
In-Reply-To: <ae3a43b0-4249-7983-9b4e-a3e3213b4436@ti.com>
On Wed, Aug 23, 2017 at 07:50:46PM +0530, Kishon Vijay Abraham I wrote:
> Greg,
>
> On Wednesday 23 August 2017 07:09 PM, Arnd Bergmann wrote:
> > Casting between an 'int' and a pointer causes a warning on
> > 64-bit architectures in compile-testing this driver:
> >
> > drivers/phy/ralink/phy-ralink-usb.c: In function 'ralink_usb_phy_probe':
> > drivers/phy/ralink/phy-ralink-usb.c:195:13: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast]
> >
> > This changes the code to cast to uintptr_t instead. This is
> > guaranteed to do what we want on all architectures and avoids
> > the warning.
> >
> > Fixes: 2411a736ff09 ("phy: ralink-usb: add driver for Mediatek/Ralink")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Can you pick this patch to fix the compiler warning.
Can you resend it to me in a format that I can apply it in?
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-23 23:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 13:39 [PATCH] phy: ralink: fix 64-bit build warning Arnd Bergmann
2017-08-23 13:49 ` John Crispin
2017-08-23 13:58 ` Kishon Vijay Abraham I
2017-08-23 13:59 ` Harvey Hunt
2017-08-23 14:20 ` Kishon Vijay Abraham I
2017-08-23 23:30 ` Greg Kroah-Hartman [this message]
2017-08-24 7:49 ` Kishon Vijay Abraham I
-- strict thread matches above, loose matches on Subject: below --
2017-08-24 7:49 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=20170823233023.GA7482@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=harvey.hunt@imgtec.com \
--cc=john@phrozen.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
/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.