linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ddutile@redhat.com (Don Dutile)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Change 'Call trace' to 'Call Trace' for tool scanners
Date: Thu, 05 Feb 2015 13:18:13 -0500	[thread overview]
Message-ID: <54D3B3E5.4010505@redhat.com> (raw)
In-Reply-To: <20150205173718.GS8656@n2100.arm.linux.org.uk>

On 02/05/2015 12:37 PM, Russell King - ARM Linux wrote:
> On Thu, Feb 05, 2015 at 12:30:27PM -0500, Donald Dutile wrote:
>> Receiving reports from service folks that arm64 uses
>> 'Call trace' when dumping stack, instead of the more familiar
>> 'Call Trace'; the former is not being seen by tools that
>> scan for the latter text.  Checking various arches,
>> it appears the mainstream server arches (ia64, mips, ppc,
>> s390, sparc, x86) use 'Call Trace'.
>> This kernel tools script scans for the latter text string as well
>>    tools/testing/selftests/rcutorture/bin/parse-console.sh
>> so it doesn't appear to be arch or vendor specific.
>
> That script should also be changed to accept "Backtrace" which we've had
> for eons on ARM.  I would not be happy to change that given that ARM has
> used "Backtrace" there for a very long time now (not far off 20 years.)
>
So you're saying:
(a) you want 'Backtrace' added to parse-console.sh
(b) 'not happy to change that' .. where 'that' == ?
-dd

  reply	other threads:[~2015-02-05 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 17:30 [PATCH] arm64: Change 'Call trace' to 'Call Trace' for tool scanners Donald Dutile
2015-02-05 17:37 ` Russell King - ARM Linux
2015-02-05 18:18   ` Don Dutile [this message]
2015-02-05 18:30     ` Russell King - ARM Linux
2015-02-05 18:46       ` Don Dutile
2015-02-06 15:34 ` Catalin Marinas
2015-02-06 18:43   ` Don Dutile

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=54D3B3E5.4010505@redhat.com \
    --to=ddutile@redhat.com \
    --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).