From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] net: rtl8169: Build warning fixes for 64-bit
Date: Wed, 21 Oct 2015 10:32:17 -0600 [thread overview]
Message-ID: <5627BE11.8030706@wwwdotorg.org> (raw)
In-Reply-To: <CANr=Z=Y47iRq2gYsbJhamQ1ARkCta=taJWxqctf9UMaFu6YKJQ@mail.gmail.com>
On 10/05/2015 10:45 AM, Joe Hershberger wrote:
> On Fri, Oct 2, 2015 at 6:44 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Casting from dev->priv to pci_dev_t changes the value's size on a 64-bit
>> system. This causes the compiler to complain about casting a pointer to an
>> integer of a different (smaller) size. To avoid this, cast to an integer
>> of matching size first, then perform an int->int cast to perform the size
>> change. This signals explicitly that we do want to change the size, and
>> avoids the compiler warning. This is legitimate since we know the pointer
>> actually stores a small integer, not a pointer value.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>
> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
Joe, this patch appears to be assigned to you in patchwork. Will you
apply it now the merge window is open, or are you assuming it will go
through the Tegra tree with all the PCIe patches?
next prev parent reply other threads:[~2015-10-21 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 23:44 [U-Boot] [PATCH] net: rtl8169: Build warning fixes for 64-bit Stephen Warren
2015-10-05 16:45 ` Joe Hershberger
2015-10-21 16:32 ` Stephen Warren [this message]
2015-10-21 21:08 ` Joe Hershberger
2015-10-29 19:32 ` Joe Hershberger
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=5627BE11.8030706@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox