From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3] powerpc/powernv Platform dump interface
Date: Wed, 05 Mar 2014 12:51:16 +1100 [thread overview]
Message-ID: <871tyhl8ff.fsf@river.au.ibm.com> (raw)
In-Reply-To: <5315C592.4050605@linux.vnet.ibm.com>
Vasant Hegde <hegdevasant@linux.vnet.ibm.com> writes:
>> + Each dump has the following files:
>> + id: An ASCII representation of the dump ID
>> + in hex (e.g. '0x01')
>> + type: An ASCII representation of the type of
>> + dump in the format "0x%x %s" with the ID
>
> Better 0x%x - %s ?
I thought of that, but figured that a simple space is probably slightly
easier to parse programatically.
next prev parent reply other threads:[~2014-03-05 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 1:58 [PATCH] powerpc/powernv Platform dump interface Stewart Smith
2014-02-26 5:42 ` [PATCH v2] " Stewart Smith
2014-03-02 23:25 ` [PATCH v3] " Stewart Smith
2014-03-04 12:22 ` Vasant Hegde
2014-03-05 1:51 ` Stewart Smith [this message]
2014-03-05 1:55 ` Stewart Smith
2014-03-05 3:25 ` Vasant Hegde
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=871tyhl8ff.fsf@river.au.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).