From: Steven Rostedt <rostedt@goodmis.org>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.osdl.org,
Glauber de Oliveira Costa <glommer@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Lguest32 print hex on bad reads and writes
Date: Wed, 04 Apr 2007 23:14:08 -0400 [thread overview]
Message-ID: <1175742848.9371.33.camel@localhost.localdomain> (raw)
In-Reply-To: <72C854B9-1A7F-44C5-9D62-B6B63F3A6DE7@mac.com>
On Wed, 2007-04-04 at 23:06 -0400, Kyle Moffett wrote:
> > (Erk, I wonder what I was thinking when I wrote that?) Can I ask
> > for %#x (or 0x%x)? I'm easily confused.
>
> How about "%p" for pointers?
But that would require casting the numbers to pointers.
-- Steve
next prev parent reply other threads:[~2007-04-05 3:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 19:14 [PATCH] Lguest32 print hex on bad reads and writes Steven Rostedt
2007-04-05 3:01 ` Rusty Russell
2007-04-05 3:06 ` Kyle Moffett
2007-04-05 3:14 ` Steven Rostedt [this message]
2007-04-05 3:34 ` Rusty Russell
2007-04-05 5:58 ` H. Peter Anvin
2007-04-05 6:17 ` H. Peter Anvin
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=1175742848.9371.33.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=glommer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.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).