linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Cort Dougan <cort@fsmlabs.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Compile fix for 4xx (linuxppc_2_4_devel)
Date: Tue, 20 Aug 2002 13:53:43 -0700	[thread overview]
Message-ID: <20020820205343.GC891@opus.bloom.county> (raw)
In-Reply-To: <20020820144707.I24379@host110.fsmlabs.com>


On Tue, Aug 20, 2002 at 02:47:07PM -0600, Cort Dougan wrote:

> } Actually, I'd rather keep it broken until either no one comments on
> } Milton's continued patching of this code (and it's implicitily OK'ed,
> } and myself or Troy will commit it), or there's comments on his changes
> } and ....
>
> I can submit patches to break other ports if you'd like that, as well.

Well, since what Troy commited came from you, IIRC, you already have. :)

But seriously, I'd rather not apply a fix for one port that still leaves
other ports broken.  Milton's patch fixes 4xx, as well as CHRP (which is
currently unhappy) along with the cleanups introduced in what he did.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2002-08-20 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20  0:45 Compile fix for 4xx (linuxppc_2_4_devel) David Gibson
2002-08-20 20:47 ` Tom Rini
2002-08-20 20:47   ` Cort Dougan
2002-08-20 20:53     ` Tom Rini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-20 12:08 Pete Smithers

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=20020820205343.GC891@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).