All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jagan Teki <jagannadh.teki@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] spi: cadence_qspi: Change to use devfdt_get_addr_index()
Date: Wed, 16 May 2018 19:03:50 +0530	[thread overview]
Message-ID: <CAD6G_RQL+5qJ_9mFPxyJ=6=PJOPBAWL9=_+t=HJJNmx-n_+5vw@mail.gmail.com> (raw)
In-Reply-To: <1525686177-49276-1-git-send-email-ley.foon.tan@intel.com>

On Mon, May 7, 2018 at 3:12 PM, Ley Foon Tan <ley.foon.tan@intel.com> wrote:
> Change to use devfdt_get_addr_index() function to get fdt address.
>
> Original code has compilation warning below:
>
> drivers/spi/cadence_qspi.c: In function ‘cadence_spi_ofdata_to_platdata’:
> drivers/spi/cadence_qspi.c:297:18: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>   plat->regbase = (void *)data[0];
>                   ^
> drivers/spi/cadence_qspi.c:298:18: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>   plat->ahbbase = (void *)data[2];

was this a coverage-tool check, I didn't see any warning with arm
compiler? make socfpga_arria5_defconfig && make

  parent reply	other threads:[~2018-05-16 13:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07  9:42 [U-Boot] [PATCH] spi: cadence_qspi: Change to use devfdt_get_addr_index() Ley Foon Tan
2018-05-07  9:42 ` [U-Boot] [PATCH] spi: cadence_qspi: Fix compilation warning Ley Foon Tan
2018-06-01  8:07   ` Marek Vasut
2018-06-01  8:23     ` Ley Foon Tan
2018-05-07  9:42 ` [U-Boot] [PATCH] spi: cadence_qspi: Fix warning cast from pointer to integer of different size Ley Foon Tan
2018-06-01  8:07   ` Marek Vasut
2018-06-01  8:24     ` Ley Foon Tan
2018-05-16 13:33 ` Jagan Teki [this message]
2018-05-17  2:23   ` [U-Boot] [PATCH] spi: cadence_qspi: Change to use devfdt_get_addr_index() Ley Foon Tan
2018-06-01  8:07 ` Marek Vasut
2018-06-01 17:02 ` Jagan Teki

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='CAD6G_RQL+5qJ_9mFPxyJ=6=PJOPBAWL9=_+t=HJJNmx-n_+5vw@mail.gmail.com' \
    --to=jagannadh.teki@gmail.com \
    --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.