Re: [PATCH] use %p for pointers

>diff --git a/drivers/sbus/char/uctrl.c b/drivers/sbus/char/uctrl.c
>index ddc0681..b30372f 100644
>--- a/drivers/sbus/char/uctrl.c
>+++ b/drivers/sbus/char/uctrl.c
>@@ -400,7 +400,7 @@ static int __init ts102_uctrl_init(void)
> 	}
> 
> 	driver->regs->uctrl_intr = UCTRL_INTR_RXNE_REQ|UCTRL_INTR_RXNE_MSK;
>-	printk("uctrl: 0x%x (irq %d)\n", driver->regs, driver->irq);
>+	printk("uctrl: 0x%p (irq %d)\n", driver->regs, driver->irq);

So what's the difference, except that %p will evaluate to (nil) or 
(null) when the argument is 0 [this is the case with glibc]?
That would print 0x(nil).


	-`J'
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] use %p for pointers
    • From: Al Viro <[email protected]>

• References:
  • [PATCH] use %p for pointers
    • From: Al Viro <[email protected]>

• Prev by Date: Re: [PATCH] arm: it's OK to pass pointer to volatile as iounmap() argument...
• Next by Date: [PATCH] block layer: elv_iosched_show should get elv_list_lock
• Previous by thread: Re: [PATCH] use %p for pointers
• Next by thread: Re: [PATCH] use %p for pointers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]