From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jeff Garzik <garzik@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] Fix starfire compiler warning on PAE
Date: Sat, 04 Jan 2003 21:08:33 -0800 [thread overview]
Message-ID: <99960000.1041743313@titus> (raw)
diff -urpN -X /home/fletch/.diff.exclude
12-boot_error/drivers/net/starfire.c
19-fix_starfire_warning/drivers/net/starfire.c
--- 12-boot_error/drivers/net/starfire.c Fri Dec 13 23:17:59 2002
+++ 19-fix_starfire_warning/drivers/net/starfire.c Thu Jan 2 22:18:18 2003
@@ -1847,15 +1847,15 @@ static int netdev_close(struct net_devic
#ifdef __i386__
if (debug > 2) {
- printk("\n"KERN_DEBUG" Tx ring at %8.8x:\n",
- np->tx_ring_dma);
+ printk("\n"KERN_DEBUG" Tx ring at %9.9Lx:\n",
+ (u64) np->tx_ring_dma);
for (i = 0; i < 8 /* TX_RING_SIZE is huge! */; i++)
printk(KERN_DEBUG " #%d desc. %8.8x %8.8x -> %8.8x.\n",
i, le32_to_cpu(np->tx_ring[i].status),
le32_to_cpu(np->tx_ring[i].first_addr),
le32_to_cpu(np->tx_done_q[i].status));
- printk(KERN_DEBUG " Rx ring at %8.8x -> %p:\n",
- np->rx_ring_dma, np->rx_done_q);
+ printk(KERN_DEBUG " Rx ring at %9.9Lx -> %p:\n",
+ (u64) np->rx_ring_dma, np->rx_done_q);
if (np->rx_done_q)
for (i = 0; i < 8 /* RX_RING_SIZE */; i++) {
printk(KERN_DEBUG " #%d desc. %8.8x -> %8.8x\n",
next reply other threads:[~2003-01-05 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 5:08 Martin J. Bligh [this message]
2003-01-06 20:57 ` [PATCH] Fix starfire compiler warning on PAE Ion Badulescu
2003-01-06 21:14 ` Martin J. Bligh
2003-01-06 21:35 ` Ion Badulescu
2003-01-06 21:45 ` Martin J. Bligh
2003-01-06 22:25 ` Ion Badulescu
2003-02-10 3:34 ` Testing new starfire driver for 2.5 Martin J. Bligh
2003-02-10 21:55 ` Ion Badulescu
2003-02-10 22:24 ` Martin J. Bligh
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=99960000.1041743313@titus \
--to=mbligh@aracnet.com \
--cc=garzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 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.