All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-embedded@lists.linuxppc.org, trini@kernel.crashing.org
Subject: Re: state of 4xx code in 2.5.x
Date: 11 Sep 2002 19:48:27 -0700	[thread overview]
Message-ID: <52u1kvditg.fsf@topspin.com> (raw)
In-Reply-To: <15743.64401.154459.318050@argo.ozlabs.ibm.com>


>>>>> "Paul" == Paul Mackerras <paulus@samba.org> writes:

    Paul> I am becoming increasingly concerned about the quality, or
    Paul> lack of it, of the 4xx code generally.  I think we need
    Paul> someone who has a good amount of experience in Linux kernel
    Paul> coding to go through all the 4xx code and clean it up and
    Paul> simplify it where possible.  I know that the 4xx family have
    Paul> quirks (e.g. DCRs) which make it difficult in places to do
    Paul> things simply, but with a bit of creativity we can make the
    Paul> code clearer and simpler than it is at the moment.

Sounds great!  I don't have the time (or the kernel hacking cred,
probably) to do much more than cheer you on, unfortunately.  However I
would suggest that you start by proposing a design before you start
moving code around.  I definitely agree that there is far too much
duplicated and confusing code, but I don't think things will improve
without a clear articulation of what belongs where (ie what goes in
include/asm-ppc/, arch/ppc/platforms/, arch/ppc/kernel/ etc., and what
the difference is between 4xx.h, 405.h, 405gp.h)

Best,
  Roland

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-09-12  2:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  2:27 state of 4xx code in 2.5.x Paul Mackerras
2002-09-12  2:48 ` Roland Dreier [this message]

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=52u1kvditg.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.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.