From: Ladislav Michl <ladis@linux-mips.org>
To: Pete Popov <ppopov@mvista.com>
Cc: Brian Murphy <brm@murphy.dk>, Ralf Baechle <ralf@linux-mips.org>,
Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: [PATCH 2.4] cpu-probe.c error
Date: Sat, 21 Jun 2003 10:06:28 +0100 [thread overview]
Message-ID: <20030621100628.A31107@ftp.linux-mips.org> (raw)
In-Reply-To: <1056128905.10307.4.camel@zeus.mvista.com>; from ppopov@mvista.com on Fri, Jun 20, 2003 at 10:08:25AM -0700
On Fri, Jun 20, 2003 at 10:08:25AM -0700, Pete Popov wrote:
>
> FYI, I had tried the same patch and it works fine on my boards. I think
> mips64 may be broken as well, if I remember correctly.
FYI, I sent patch which fixes mips/mips64; 2.4/2.5 at Mon, 16 Jun 2003
16:13:07 +0200 with subject "[PATCH] cpu-probe compile fix" and
Message-ID: <20030616141307.GA16721@simek>
Ralf could you please apply that one?
ladis
prev parent reply other threads:[~2003-06-21 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-20 17:02 [PATCH 2.4] cpu-probe.c error Brian Murphy
2003-06-20 17:08 ` Pete Popov
2003-06-21 9:06 ` Ladislav Michl [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=20030621100628.A31107@ftp.linux-mips.org \
--to=ladis@linux-mips.org \
--cc=brm@murphy.dk \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@mvista.com \
--cc=ralf@linux-mips.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