From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ehci-hcd: fix warnings on 64-bit builds
Date: Fri, 20 Mar 2015 14:19:56 +0100 [thread overview]
Message-ID: <201503201419.56356.marex@denx.de> (raw)
In-Reply-To: <1426625199-14127-3-git-send-email-robh@kernel.org>
On Tuesday, March 17, 2015 at 09:46:37 PM, Rob Herring wrote:
> Change addresses to unsigned long to be compatible with 64-bit builds.
> Regardless of fixing warnings, the device is still only 32-bit capable.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Cc: Marek Vasut <marex@denx.de>
> ---
> drivers/usb/host/ehci-hcd.c | 82
> ++++++++++++++++++++++----------------------- 1 file changed, 41
> insertions(+), 41 deletions(-)
Hi,
I will handle those patches in a couple of days. I got similar fix
from Thierry today in a patchset, this is the subject:
[PATCH 11/13] usb: ehci-hcd: Build warning fixes for 64-bit
I would obviously like to pick Rob's one, since it came first, but
I will need to check if they're really the same. Moreover, shall I
pick this for the current release or is it OK to apply for the next
one ?
Thanks !
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-03-20 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:46 [U-Boot] [PATCH] usb: ci_udc: fix warnings on 64-bit builds Rob Herring
2015-03-17 20:46 ` [U-Boot] [PATCH] mv_i2c: " Rob Herring
2015-03-18 8:14 ` Heiko Schocher
2015-03-17 20:46 ` [U-Boot] [PATCH] ehci-hcd: " Rob Herring
2015-03-20 13:19 ` Marek Vasut [this message]
2015-03-23 23:36 ` Rob Herring
2015-03-24 15:42 ` Marek Vasut
2015-03-25 12:29 ` Thierry Reding
2015-03-25 12:37 ` Marek Vasut
2015-03-25 11:49 ` Marek Vasut
2015-03-17 20:46 ` [U-Boot] [PATCH] sdhci: " Rob Herring
2015-03-18 7:55 ` Pantelis Antoniou
2015-03-17 20:46 ` [U-Boot] [PATCH] mv_sdhci: " Rob Herring
2015-03-18 7:55 ` Pantelis Antoniou
2015-03-23 9:24 ` [U-Boot] [PATCH] usb: ci_udc: " Lukasz Majewski
2015-03-25 11:47 ` Marek Vasut
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=201503201419.56356.marex@denx.de \
--to=marex@denx.de \
--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