From: Ralf Baechle <ralf@oss.sgi.com>
To: Matthew Dharm <mdharm@momenco.com>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: PATCH: Momentum Computer Ocelot: Making the latest CVS tree build
Date: Mon, 14 May 2001 22:05:35 -0300 [thread overview]
Message-ID: <20010514220535.D9945@bacchus.dhis.org> (raw)
In-Reply-To: <NEBBLJGMNKKEEMNLHGAIGEGOCBAA.mdharm@momenco.com>; from mdharm@momenco.com on Mon, May 14, 2001 at 04:35:43PM -0700
On Mon, May 14, 2001 at 04:35:43PM -0700, Matthew Dharm wrote:
> Attached is a patch against the latest CVS tree (as of about 3 hours
> ago). It makes the Momentum Computer Ocelot board build again --
> apparently, some of the PCI code has been changed.
Except your patch doesn't even touch the PCI but interrupt code.
> It seems likely to me that this is not the best way to do this
> patch... if it's unacceptable to the powers that be (Ralf?), could
> someone point out to me the new convention for board-specific PCI
> initialization?
Applied, but without the two extra junk segment in the patch.
Ralf
prev parent reply other threads:[~2001-05-15 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 23:35 PATCH: Momentum Computer Ocelot: Making the latest CVS tree build Matthew Dharm
2001-05-15 1:05 ` Ralf Baechle [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=20010514220535.D9945@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.com \
/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.