From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] scripts: add ARM support to decodecode
Date: Tue, 5 Jan 2010 17:31:20 +0000 [thread overview]
Message-ID: <20100105173120.GA10941@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100105070658.766317d2@linux.intel.com>
On Tue, Jan 05, 2010 at 07:06:58AM -0800, Arjan van de Ven wrote:
> I'm fine with this, but I wonder if ARM could switch to the <>
> convention for the faulting instruction, just to keep things
> consistent..
I did mention exactly that on the previous review round on this patch;
the problem is that it won't change older kernels, and if anyone is
still using ksymoops or similar parsing stuff, it could break on
such a change.
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Rabin Vincent <rabin@rab.in>,
mmarek@suse.cz, linux-kernel@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
wangcong@zeuux.org, akpm@linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] scripts: add ARM support to decodecode
Date: Tue, 5 Jan 2010 17:31:20 +0000 [thread overview]
Message-ID: <20100105173120.GA10941@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100105070658.766317d2@linux.intel.com>
On Tue, Jan 05, 2010 at 07:06:58AM -0800, Arjan van de Ven wrote:
> I'm fine with this, but I wonder if ARM could switch to the <>
> convention for the faulting instruction, just to keep things
> consistent..
I did mention exactly that on the previous review round on this patch;
the problem is that it won't change older kernels, and if anyone is
still using ksymoops or similar parsing stuff, it could break on
such a change.
next prev parent reply other threads:[~2010-01-05 17:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 14:53 [PATCH] scripts: add ARM support to decodecode Rabin Vincent
2009-12-30 14:53 ` Rabin Vincent
2009-12-31 5:18 ` Simon Horman
2009-12-31 5:18 ` Simon Horman
2010-01-05 14:57 ` [PATCH v2] " Rabin Vincent
2010-01-05 14:57 ` Rabin Vincent
2010-01-05 15:06 ` Arjan van de Ven
2010-01-05 15:06 ` Arjan van de Ven
2010-01-05 15:34 ` Michal Marek
2010-01-05 15:34 ` Michal Marek
2010-01-05 17:31 ` Russell King - ARM Linux [this message]
2010-01-05 17:31 ` Russell King - ARM Linux
2010-01-05 19:27 ` Daniel Jacobowitz
2010-01-05 19:27 ` Daniel Jacobowitz
2010-01-05 22:14 ` Simon Horman
2010-01-05 22:14 ` Simon Horman
2010-01-01 20:32 ` [PATCH] " Russell King - ARM Linux
2010-01-01 20:32 ` Russell King - ARM Linux
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=20100105173120.GA10941@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.