linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Patches for ppc?
Date: Tue, 21 Aug 2007 17:14:41 +0200	[thread overview]
Message-ID: <ae3d7296a5c3e83f19817a04841d099f@kernel.crashing.org> (raw)
In-Reply-To: <20070821052514.GC21169@localhost.localdomain>

> It's not a question of indivudual files being copied over - things are
> done differently in arch/powerpc.  Things are gradually being ported
> over to arch/powerpc as people get the time - that's why arch/ppc
> isn't gone yet.

And to be blunt, one of the points of arch/powerpc vs. arch/ppc is
to actually leave behind some stuff.  "If no one ports it, no one
wants it".


Segher

  reply	other threads:[~2007-08-21 15:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17  7:43 Patches for ppc? Johan Borkhuis
2007-08-17  8:00 ` Kumar Gala
2007-08-17 12:26 ` David Woodhouse
2007-08-17 14:36   ` Johan Borkhuis
2007-08-17 14:40     ` David Woodhouse
2007-08-17 14:43       ` Johan Borkhuis
2007-08-17 23:28         ` Satya
2007-08-21  5:25           ` David Gibson
2007-08-21 15:14             ` Segher Boessenkool [this message]
2007-08-21 16:11               ` Phil Terry
2007-08-21 16:35                 ` Josh Boyer
2007-08-21 16:40                 ` Kumar Gala
2007-08-21 17:12                   ` Phil Terry
2007-08-21 17:30                     ` Scott Wood
2007-08-21 18:09                     ` Segher Boessenkool
2007-08-21 17:22                 ` Linas Vepstas

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=ae3d7296a5c3e83f19817a04841d099f@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=dwmw2@infradead.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).