From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Prefix revision number in /proc/cpuinfo
Date: Thu, 12 Nov 2009 23:03:14 +0100 [thread overview]
Message-ID: <20091112220314.GS14091@buzzloop.caiaq.de> (raw)
In-Reply-To: <20091112215201.GA12308@n2100.arm.linux.org.uk>
Hi Russell,
On Thu, Nov 12, 2009 at 09:52:01PM +0000, Russell King - ARM Linux wrote:
> On Thu, Nov 12, 2009 at 02:58:07PM +0100, Daniel Mack wrote:
> > The revision field in /proc/cpuinfo is reported as hex number, so it
> > should have a '0x' prefix to make that clear. Otherwise, parsers
> > will take it as decimal number unless it contains a letter.
>
> So what you're doing is possibly breaking existing parsers (which
> probably already assume it is hex) to fix buggy parsers?
I wouldn't call that fixing a buggy parser. On my board, the revision is
0x101 which was parsed as 101. You can't know it is in hex unless you
look at the sources.
Daniel
next prev parent reply other threads:[~2009-11-12 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 13:58 [PATCH] ARM: Prefix revision number in /proc/cpuinfo Daniel Mack
2009-11-12 14:30 ` Alessandro Rubini
2009-11-12 14:37 ` Daniel Mack
2009-11-12 21:52 ` Russell King - ARM Linux
2009-11-12 22:03 ` Daniel Mack [this message]
2009-11-12 22:13 ` Russell King - ARM Linux
2009-11-12 23:17 ` Daniel Mack
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=20091112220314.GS14091@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.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).