Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: [ralf@linux-mips.org: CVS Update@-mips.org: linux]
Date: Mon, 19 Jan 2004 11:05:06 -0800	[thread overview]
Message-ID: <20040119110506.C14131@mvista.com> (raw)


This check-in seems to break malta build.

arch/mips/mips-boards/malta/malta_int.c: In function `mips_pcibios_iack':
arch/mips/mips-boards/malta/malta_int.c:63: error: `MIPS_REVISION_CORID_CORE_FPGA2' undeclared (first use in this function)
arch/mips/mips-boards/malta/malta_int.c:63: error: (Each undeclared identifier is reported only once
...

Jun

----- Forwarded message from ralf@linux-mips.org -----

X-Sieve: CMU Sieve 2.2
Delivered-To: jsun@mvista.com
From: ralf@linux-mips.org
To: linux-cvs@linux-mips.org
Subject: CVS Update@-mips.org: linux 
Date: Mon, 19 Jan 2004 16:47:25 +0000
X-archive-position: 3587
X-ecartis-version: Ecartis v1.0.0
Errors-to: linux-cvs-bounce@linux-mips.org
X-original-sender: ralf@linux-mips.org
Precedence: bulk
Reply-to: linux-mips@linux-mips.org
X-list: linux-cvs
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=AWL,BAYES_30,NO_REAL_NAME
	version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)


CVSROOT:	/home/cvs
Module name:	linux
Changes by:	ralf@ftp.linux-mips.org	04/01/19 16:47:25

Modified files:
	arch/mips/mips-boards/malta: malta_int.c malta_setup.c 

Log message:
	More Malta updates.



----- End forwarded message -----

             reply	other threads:[~2004-01-19 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 19:05 Jun Sun [this message]
2004-01-19 19:20 ` [ralf@linux-mips.org: CVS Update@-mips.org: linux] Ralf Baechle

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=20040119110506.C14131@mvista.com \
    --to=jsun@mvista.com \
    --cc=linux-mips@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