public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: akpm <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>,
	ak@suse.de, tony.luck@intel.com
Subject: [PATCH] swiotlb: fix gcc printk warning
Date: Fri, 14 Jan 2005 12:39:12 -0800	[thread overview]
Message-ID: <41E82DF0.5020600@osdl.org> (raw)

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


swiotlb: Fix gcc printk format warning on x86_64, OK for ia64:
arch/ia64/lib/swiotlb.c:351: warning: long unsigned int format, long 
long unsigned int arg (arg 2)

Signed-off-by: Randy Dunlap <rddunlap@osdl.org>

diffstat:=
  arch/ia64/lib/swiotlb.c |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

---

[-- Attachment #2: swiotlb_printk.patch --]
[-- Type: text/x-patch, Size: 702 bytes --]


diff -Naurp ./arch/ia64/lib/swiotlb.c~swiotlb_types ./arch/ia64/lib/swiotlb.c
--- ./arch/ia64/lib/swiotlb.c~swiotlb_types	2005-01-10 10:38:39.310529184 -0800
+++ ./arch/ia64/lib/swiotlb.c	2005-01-14 11:53:17.991480232 -0800
@@ -347,8 +347,8 @@ swiotlb_alloc_coherent(struct device *hw
 
 	/* Confirm address can be DMA'd by device */
 	if (address_needs_mapping(hwdev, dev_addr)) {
-		printk("hwdev DMA mask = 0x%016lx, dev_addr = 0x%016lx\n",
-		       *hwdev->dma_mask, dev_addr);
+		printk("hwdev DMA mask = 0x%016Lx, dev_addr = 0x%016lx\n",
+		       (unsigned long long)*hwdev->dma_mask, dev_addr);
 		panic("swiotlb_alloc_coherent: allocated memory is out of "
 		      "range for device");
 	}

             reply	other threads:[~2005-01-14 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 20:39 Randy.Dunlap [this message]
2005-01-15  0:11 ` [PATCH] swiotlb: fix gcc printk warning Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-01-15  0:17 Luck, Tony

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=41E82DF0.5020600@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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