LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Becky Bruce <beckyb@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	jeff@garzik.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] sata_fsl: Fix compile warnings
Date: Wed, 13 May 2009 16:20:11 -0500	[thread overview]
Message-ID: <B2706AD9-61E9-49E2-8EA4-6DB69B608658@kernel.crashing.org> (raw)
In-Reply-To: <1242249131-25014-1-git-send-email-galak@kernel.crashing.org>


On May 13, 2009, at 4:12 PM, Kumar Gala wrote:

> We we build with dma_addr_t as a 64-bit quantity we get:
>
> drivers/ata/sata_fsl.c: In function 'sata_fsl_fill_sg':
> drivers/ata/sata_fsl.c:340: warning: format '%x' expects type  
> 'unsigned int', but argument 4 has type 'dma_addr_t'
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> drivers/ata/sata_fsl.c |    7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/ata/sata_fsl.c b/drivers/ata/sata_fsl.c
> index c2e90e1..c7ee52d 100644
> --- a/drivers/ata/sata_fsl.c
> +++ b/drivers/ata/sata_fsl.c
> @@ -332,13 +332,14 @@ static unsigned int sata_fsl_fill_sg(struct  
> ata_queued_cmd *qc, void *cmd_desc,
> 		dma_addr_t sg_addr = sg_dma_address(sg);
> 		u32 sg_len = sg_dma_len(sg);
>
> -		VPRINTK("SATA FSL : fill_sg, sg_addr = 0x%x, sg_len = %d\n",
> -			sg_addr, sg_len);
> +		VPRINTK("SATA FSL : fill_sg, sg_addr = 0x%llx, sg_len = %d\n",
> +			(unsigned long long)sg_addr, sg_len);
>
> 		/* warn if each s/g element is not dword aligned */
> 		if (sg_addr & 0x03)
> 			ata_port_printk(qc->ap, KERN_ERR,
> -					"s/g addr unaligned : 0x%x\n", sg_addr);
> +					"s/g addr unaligned : 0x%llxx\n",

You have an extra "x" in there....

Cheers,
B

      reply	other threads:[~2009-05-13 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 21:12 [PATCH] sata_fsl: Fix compile warnings Kumar Gala
2009-05-13 21:20 ` Becky Bruce [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=B2706AD9-61E9-49E2-8EA4-6DB69B608658@kernel.crashing.org \
    --to=beckyb@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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