Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: [PATCH] Fix O2/IP32 compile time glitch
Date: Mon, 21 Jun 2004 02:10:04 -0400	[thread overview]
Message-ID: <40D67BBC.4020901@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 362 bytes --]

Seems somewhere between 2.6.6 and 2.6.7, something happened that makes 
IP32's build die in drivers/char/rtc.c when trying to reference 
MACEISA_RTC_IRQ.  The attached patch fixes it.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

[-- Attachment #2: mipscvs-2.6.7-maceisa_rtc_irq-fix.patch --]
[-- Type: text/plain, Size: 339 bytes --]

--- include/asm-mips/mach-ip32/mc146818rtc.h.orig	2004-06-21 00:47:35.931657976 -0400
+++ include/asm-mips/mach-ip32/mc146818rtc.h	2004-06-21 00:47:50.704412176 -0400
@@ -13,6 +13,7 @@
 
 #include <asm/io.h>
 #include <asm/ip32/mace.h>
+#include <asm/ip32/ip32_ints.h>
 
 #define RTC_PORT(x)	(0x70 + (x))
 #define RTC_IRQ		MACEISA_RTC_IRQ

                 reply	other threads:[~2004-06-21  6:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40D67BBC.4020901@gentoo.org \
    --to=kumba@gentoo.org \
    --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