From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v2] declance: Fix 64-bit compilation warnings
Date: Thu, 3 Jul 2014 03:34:04 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.11.1407030331550.15455@eddie.linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.11.1407030244230.15455@eddie.linux-mips.org>
On Thu, 3 Jul 2014, Maciej W. Rozycki wrote:
> > > @@ -499,8 +499,9 @@ static void lance_init_ring(struct net_d
> > > /* The ones required by tmd2 */
> > > *lib_ptr(ib, btx_ring[i].misc, lp->type) = 0;
> > > if (i < 3 && ZERO)
> > > - printk("%d: 0x%8.8x(0x%8.8x)\n",
> > > - i, leptr, (uint)lp->tx_buf_ptr_cpu[i]);
> > > + printk("%d: 0x%8.8x(%#0*lx)\n",
> > > + i, leptr, 2 * (int)sizeof(long) + 2,
> > > + (long)lp->tx_buf_ptr_cpu[i]);
> >
> > Please just use "%p", no casts required.
>
> Hmm, there was something about %p that made me reject it, however I can't
> recall what it was and I can get the desired output with this format
> specifier (the NULL special case difference can be ignored, the pointers
> printed here won't ever be NULL). Sending an update right away.
Ah, there it is:
drivers/net/ethernet/amd/declance.c: In function 'lance_init_ring':
drivers/net/ethernet/amd/declance.c:503: warning: '#' flag used with '%p' printf format
drivers/net/ethernet/amd/declance.c:520: warning: '#' flag used with '%p' printf format
That's obviously GCC's incompatibility to our implementation. I'm not
sure if that can be worked around, but I'll see what I can do about it.
Maciej
next prev parent reply other threads:[~2014-07-03 2:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 2:10 [PATCH v2] declance: Fix 64-bit compilation warnings Maciej W. Rozycki
2014-07-03 1:28 ` David Miller
2014-07-03 2:29 ` Maciej W. Rozycki
2014-07-03 2:34 ` Maciej W. Rozycki [this message]
2014-07-03 3:05 ` Joe Perches
2014-07-03 4:51 ` Maciej W. Rozycki
2014-07-03 5:16 ` Joe Perches
2014-07-03 6:01 ` Maciej W. Rozycki
2014-07-03 6:25 ` Joe Perches
2014-07-03 16:57 ` Grant Likely
2014-07-05 14:56 ` Maciej W. Rozycki
2014-07-05 16:07 ` Joe Perches
2014-07-05 17:39 ` Maciej W. Rozycki
2014-07-05 18:08 ` Joe Perches
2014-07-05 18:20 ` Maciej W. Rozycki
2014-07-05 18:31 ` Joe Perches
2014-07-05 20:25 ` Maciej W. Rozycki
2014-07-05 20:45 ` [PATCH] vsprintf: Remove SPECIAL from pointer types Joe Perches
2014-07-06 11:44 ` Maciej W. Rozycki
2014-07-06 14:32 ` Joe Perches
2014-07-07 8:26 ` David Laight
2014-07-07 13:26 ` Joe Perches
2014-07-07 12:01 ` [PATCH v2] declance: Fix 64-bit compilation warnings Grant Likely
2014-07-07 12:18 ` Maciej W. Rozycki
2014-07-07 13:40 ` Joe Perches
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=alpine.LFD.2.11.1407030331550.15455@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=netdev@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 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).