All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Compile fix for 4xx (linuxppc_2_4_devel)
Date: Tue, 20 Aug 2002 14:47:07 -0600	[thread overview]
Message-ID: <20020820144707.I24379@host110.fsmlabs.com> (raw)
In-Reply-To: <20020820204731.GB891@opus.bloom.county>; from trini@kernel.crashing.org on Tue, Aug 20, 2002 at 01:47:31PM -0700


I can submit patches to break other ports if you'd like that, as well.

} 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 ....

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

  reply	other threads:[~2002-08-20 20:47 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 [this message]
2002-08-20 20:53     ` Tom Rini
  -- 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=20020820144707.I24379@host110.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.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.