From: Ragnar Hojland Espinosa <ragnar@jazzfree.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org
Subject: Re: silly [< >] and other excess
Date: Thu, 23 Nov 2000 04:11:49 +0100 [thread overview]
Message-ID: <20001123041149.A17763@macula.net> (raw)
In-Reply-To: <200011222354.eAMNs1564115@saturn.cs.uml.edu> <200011230026.AAA02848@raistlin.arm.linux.org.uk>
In-Reply-To: <200011230026.AAA02848@raistlin.arm.linux.org.uk>; from Russell King on Thu, Nov 23, 2000 at 12:26:30AM +0000
On Thu, Nov 23, 2000 at 12:26:30AM +0000, Russell King wrote:
> Albert D. Cahalan writes:
> > > Function entered at [<c2800060>] from [<c0026194>]
> > > Function entered at [<c0025ac0>] from [<c0016860>]
> > > Code: e51f2024 e5923000 (e5813000) e3a00000 e51f3030
> >
> > All those numbers get looked up. Keep going for another 25 lines too.
>
> Oh, missed this one. Here you're wrong again. The numbers in [< >]
> should be looked up, and no others. The code can look exactly like
> a kernel address. In this case you definitely do NOT want to have
> them converted.
Okay. How about just using some prefix to the hex number, such as '>'?
It'll still save plenty of space, and would be trivial changes for the
tools.
--
____/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and madness await thee at its end." hkp://keys.pgp.com
Handle via comment channels only.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-23 3:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 19:00 silly [< >] and other excess Andries.Brouwer
2000-11-22 23:16 ` Russell King
2000-11-22 23:54 ` Albert D. Cahalan
2000-11-23 0:10 ` Russell King
2000-11-23 2:54 ` Albert D. Cahalan
2000-11-23 3:03 ` Keith Owens
2000-11-23 12:39 ` Albert D. Cahalan
2000-11-23 12:46 ` Alan Cox
2000-11-23 19:46 ` Russell King
2000-11-23 7:53 ` Russell King
2000-11-25 4:33 ` Albert D. Cahalan
2000-11-25 9:17 ` Russell King
2000-11-25 10:26 ` Albert D. Cahalan
2000-11-25 11:07 ` Keith Owens
2000-11-25 12:18 ` Albert D. Cahalan
2000-11-25 18:20 ` silly [< >] Guest section DW
2000-11-24 8:09 ` Pavel Machek
2000-11-25 12:11 ` silly [< >] and other excess Russell King
2000-11-27 22:02 ` Peter Samuelson
2000-11-27 22:35 ` Keith Owens
2000-11-27 23:01 ` bread in fat_access failed Nerijus Baliunas
2000-11-27 23:11 ` Nerijus Baliunas
2000-11-28 9:16 ` silly [< >] and other excess Christian Gennerat
2000-11-23 0:26 ` Russell King
2000-11-23 3:11 ` Ragnar Hojland Espinosa [this message]
2000-11-23 7:55 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2000-11-23 2:24 Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16 ` Tuomas Heino
2000-11-23 0:38 Andries.Brouwer
2000-11-23 0:51 ` Alan Cox
2000-11-22 13:20 [PATCH] isofs/inode.c Andries.Brouwer
2000-11-22 13:42 ` silly [< >] and other excess Christian Gennerat
2000-11-22 16:00 ` Russell King
2000-11-22 22:22 ` Keith Owens
2000-11-22 23:32 ` Albert D. Cahalan
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=20001123041149.A17763@macula.net \
--to=ragnar@jazzfree.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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