From: Eugene Surovegin <ebs@ebshome.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Make ARCH=ppc build again with new syscall path
Date: Sun, 27 Nov 2005 21:02:02 -0800 [thread overview]
Message-ID: <20051128050202.GA23652@gate.ebshome.net> (raw)
In-Reply-To: <17290.28508.336476.478948@cargo.ozlabs.ibm.com>
On Mon, Nov 28, 2005 at 01:45:48PM +1100, Paul Mackerras wrote:
>
> What do people think? Do we make ARCH=ppc use more and more stuff
> from arch/powerpc, and delete the duplicates from arch/ppc, or do
> people want to be conservative and keep arch/ppc largely unchanged?
> (I would prefer the former, myself.)
I thought initial idea was to keep arch/ppc mostly unchanged (we are in
"stable" series after all :), and migrate code to arch/powerpc when
it's ready.
Personally, the amount of PPC/PPC64 changes in 2.6 make me nervous,
looks like I'll stick with 2.4 longer than I thought for production.
--
Eugene
next prev parent reply other threads:[~2005-11-28 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 14:44 [PATCH] Make ARCH=ppc build again with new syscall path David Woodhouse
2005-11-28 2:45 ` Paul Mackerras
2005-11-28 5:02 ` Eugene Surovegin [this message]
2005-11-28 10:12 ` David Woodhouse
2005-11-28 11:01 ` Wolfgang Denk
2005-11-28 11:28 ` David Woodhouse
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=20051128050202.GA23652@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).