All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: dwc3: Fix warnings on 64-bit builds
Date: Fri, 30 Oct 2015 17:27:02 +0100	[thread overview]
Message-ID: <201510301727.02211.marex@denx.de> (raw)
In-Reply-To: <a58c12eea7bc21927ebf731750b0fa8a0be0f12c.1446218642.git.michal.simek@xilinx.com>

On Friday, October 30, 2015 at 04:24:06 PM, Michal Simek wrote:
> Change aritmentics to use 64bit types to be compatible with 64bit
> builds.
> 
> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
> ---
> 
>  drivers/usb/dwc3/core.c   |  7 ++++---
>  drivers/usb/dwc3/ep0.c    | 10 +++++-----
>  drivers/usb/dwc3/gadget.c | 10 +++++-----
>  drivers/usb/dwc3/io.h     |  4 ++--
>  4 files changed, 16 insertions(+), 15 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index ab3c94e51275..0ae3de5c27b9 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -281,7 +281,7 @@ static int dwc3_setup_scratch_buffers(struct dwc3 *dwc)
>  	return 0;
> 
>  err1:
> -	dma_unmap_single((void *)dwc->scratch_addr, dwc->nr_scratch *
> +	dma_unmap_single((void *)(uintptr_t)dwc->scratch_addr, dwc->nr_scratch *

Is this double type-cast necessary ?

>  			 DWC3_SCRATCHBUF_SIZE, DMA_BIDIRECTIONAL);
> 
>  err0:

[...]

Best regards,
Marek Vasut

  reply	other threads:[~2015-10-30 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 15:24 [U-Boot] [PATCH] usb: dwc3: Fix warnings on 64-bit builds Michal Simek
2015-10-30 16:27 ` Marek Vasut [this message]
2015-11-02  7:13   ` Michal Simek
2015-11-02 18:20     ` Marek Vasut
2015-11-03  7:20       ` Michal Simek
2015-11-03 16:30         ` Marek Vasut
2015-11-03 10:15 ` Lukasz Majewski

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=201510301727.02211.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 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.