From: Cort Dougan <cort@fsmlabs.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: [PATCH] Fix pcore build in latest linuxppc_2_4_devel
Date: Fri, 28 Jun 2002 12:35:55 -0600 [thread overview]
Message-ID: <20020628123555.F3851@host110.fsmlabs.com> (raw)
If anyone wants the BK patch, drop me a note.
diff -Nru a/BitKeeper/etc/logging_ok b/BitKeeper/etc/logging_ok
--- a/BitKeeper/etc/logging_ok Fri Jun 28 12:34:45 2002
+++ b/BitKeeper/etc/logging_ok Fri Jun 28 12:34:45 2002
@@ -50,3 +50,4 @@
trini@entropy.crashing.org
trini@opus.bloom.county
trini@stevedallas.bloom.county
+cort@host110.fsmlabs.com
diff -Nru a/arch/ppc/platforms/pcore_setup.c b/arch/ppc/platforms/pcore_setup.c
--- a/arch/ppc/platforms/pcore_setup.c Fri Jun 28 12:34:45 2002
+++ b/arch/ppc/platforms/pcore_setup.c Fri Jun 28 12:34:45 2002
@@ -167,13 +167,13 @@
for ( i = 0 ; i < 16 ; i++ )
irq_desc[i].handler = &i8259_pic;
- i8259_init(NULL);
+ i8259_init(0);
}
static int
pcore_get_irq(struct pt_regs *regs)
{
- return i8259_poll();
+ return i8259_poll(regs);
}
/*
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-06-28 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-28 18:35 Cort Dougan [this message]
2002-07-01 13:55 ` [PATCH] Fix pcore build in latest linuxppc_2_4_devel Tom Rini
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=20020628123555.F3851@host110.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).