linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"\"Richard Röjfors\"" <richard.rojfors@mocean-labs.com>,
	spi-devel-general@lists.sourceforge.net
Subject: Re: linux-next: spi tree build warning
Date: Thu, 26 Nov 2009 01:35:05 +1100	[thread overview]
Message-ID: <20091126013505.037e5751.sfr@canb.auug.org.au> (raw)
In-Reply-To: <fa686aa40911250630h764c4f26xb2e7cc735261e987@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Hi Grant,

On Wed, 25 Nov 2009 07:30:19 -0700 Grant Likely <grant.likely@secretlab.ca> wrote:
>
> Trivial fix committed to next-spi branch:
> 
> diff --git a/drivers/spi/xilinx_spi.c b/drivers/spi/xilinx_spi.c
> index b927812..9f38637 100644
> --- a/drivers/spi/xilinx_spi.c
> +++ b/drivers/spi/xilinx_spi.c
> @@ -408,8 +408,8 @@ struct spi_master *xilinx_spi_init(struct device *dev, struc
>                 goto free_irq;
>         }
> 
> -       dev_info(dev, "at 0x%08X mapped to 0x%08X, irq=%d\n",
> -               (u32)mem->start, (u32)xspi->regs, xspi->irq);
> +       dev_info(dev, "at 0x%08llX mapped to 0x%p, irq=%d\n",
> +               (unsigned long long)mem->start, xspi->regs, xspi->irq);
>         return master;

Thanks.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-11-25 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091125212959.601673f5.sfr@canb.auug.org.au>
2009-11-25 14:30 ` linux-next: spi tree build warning Grant Likely
2009-11-25 14:35   ` Stephen Rothwell [this message]

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=20091126013505.037e5751.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=richard.rojfors@mocean-labs.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).