From: benh@kernel.crashing.org
To: <msokolov@ivan.Harhan.ORG>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Incoming to helium.harhan.org:/home/linuxppc/linuxppc_2_4_alt
Date: Mon, 8 Apr 2002 19:02:25 +0100 [thread overview]
Message-ID: <20020408180225.10676@mailhost.mipsys.com> (raw)
In-Reply-To: <0204081705.AA21087@ivan.Harhan.ORG>
>
>And I'm hoping that some day PReP will be part of CONFIG_GENERIC_PPC32. See
>BenH's response about putting CONFIG_ALL_PPC to rest and converting to
>CONFIG_GENERIC_PPC32.
Yes, I've started doing that on a _devel code base, then figured out that
I had to cleanup a few crap remaining in pmac/chrp/prep, and that it would
rather be in 2.5 (we can still backport later).
So I'll start again on 2.5 this week but only for pmac/prep/chrp, I'll let
the various board maintainers decide wether to move their board under the
CONFIG_GENERIC_PPC32 umbrella or not.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-08 18:02 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
[not found] ` <0204081705.AA21087@ivan.Harhan.ORG>
2002-04-08 18:02 ` benh [this message]
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=20020408180225.10676@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=msokolov@ivan.Harhan.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).