From: Sam Ravnborg <sam@ravnborg.org>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: kai@germaschewski.name, linux-kernel@vger.kernel.org
Subject: Re: ./scripts/kallsyms.c question
Date: Mon, 10 Jul 2006 05:10:08 +0200 [thread overview]
Message-ID: <20060710031008.GA5381@mars.ravnborg.org> (raw)
In-Reply-To: <6.1.1.1.0.20060709193540.01ec8370@ptg1.spd.analog.com>
On Sun, Jul 09, 2006 at 10:26:39PM -0400, Robin Getz wrote:
> The application kallsyms generate assembler source containing symbol
> information, where "symbol information" is in these pre-defined names:
>
> _stext, _etext, _sinittext, _einittext, _sextratext, _eextratext
>
> I am working with a processor (Blackfin) which uses these plus two others
> _stext_l1, and _etext_l1.
>
> I can add these in the same fashion as the existing (see below), but was
> wondering if this shouldn't be re-structured with a struct/loop rather than
> the existing n lines of if/else?
Keep the existing if/else - it is still readable.
But please add a comment describing that it is blackfin that requires
these two odd sections.
Sam
next prev parent reply other threads:[~2006-07-10 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 2:26 Robin Getz
2006-07-10 3:10 ` Sam Ravnborg [this message]
2006-07-10 6:36 ` Robin Getz
2006-07-13 19:23 ` Sam Ravnborg
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=20060710031008.GA5381@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=kai@germaschewski.name \
--cc=linux-kernel@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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
all inboxes | Powered by JetHome®