From: benh@kernel.crashing.org
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Linux/PPC BK repository <linuxppc@helium.Harhan.ORG>,
<linuxppc-commit@source.mvista.com>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt
Date: Tue, 9 Apr 2002 12:08:30 +0200 [thread overview]
Message-ID: <20340715221138.20391@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0204091013120.13709-100000@lisianthus.sonytel.be>
>
>> Yes, though it will be separated from the actual code, and I'm
>> thinking about eventually auto-generating it.
>
>Or put the pointers to the ppc_md structs in a new section, cfr. the
>module_init() stuff.
>
Right. That's the best solution for now. Though I may still do some
local code munging as I want to see how feasible it is to have _machine
be #defined instead of beeing a variable when only one board is selected
in the config, and without having to write a #ifdef mess in a .h for each
new board added.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-09 10:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204060739.g367duV18841@helium.Harhan.ORG>
2002-04-08 15:20 ` Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt Tom Rini
2002-04-08 17:58 ` benh
2002-04-08 18:57 ` Tom Rini
2002-04-08 18:40 ` Benjamin Herrenschmidt
2002-04-09 8:14 ` Geert Uytterhoeven
2002-04-09 10:08 ` benh [this message]
[not found] ` <0204081705.AA21087@ivan.Harhan.ORG>
2002-04-08 18:02 ` benh
2002-04-09 14:52 ` Tom Rini
2002-04-09 19:23 ` Michael Sokolov
2002-04-09 19:47 ` Tom Rini
2002-04-09 20:05 ` Michael Sokolov
2002-04-09 20:15 ` Daniel Jacobowitz
2002-04-10 15:09 ` Tom Rini
2002-04-11 3:11 ` Michael Sokolov
2002-04-11 15:29 ` Tom Rini
2002-04-15 16:54 ` Troy Benjegerdes
2002-04-15 18:11 Michael Sokolov
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=20340715221138.20391@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-commit@source.mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc@helium.Harhan.ORG \
--cc=trini@kernel.crashing.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.