From: Jes Sorensen <jes@linuxcare.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Mac/m68k patches?
Date: 12 Dec 2000 19:11:47 +0100 [thread overview]
Message-ID: <d3bsuhldb0.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Geert Uytterhoeven's message of "Tue, 12 Dec 2000 10:12:18 +0100 (MET)"
>>>>> "Geert" == Geert Uytterhoeven <geert@linux-m68k.org> writes:
Geert> Hi, I have these Mac/m68k patches in my patchqueue which
Geert> affect PowerMac as well. Anyone who has a problem with them,
Geert> or can I send them to Linus?
>diff -urN linux-2.4.0-test12/drivers/macintosh/adbhid.c linux-m68k-2.4.0-test12/drivers/macintosh/adbhid.c
>--- linux-2.4.0-test12/drivers/macintosh/adbhid.c Sun Sep 17 18:48:05 2000
>+++ linux-m68k-2.4.0-test12/drivers/macintosh/adbhid.c Tue Dec 12 09:02:45 2000
>@@ -855,8 +855,10 @@
>
> static int __init adbhid_init(void)
> {
>+#ifndef CONFIG_MAC
> if ( (_machine != _MACH_chrp) && (_machine != _MACH_Pmac) )
> return 0;
>+#endif
>
> led_request.complete = 1;
>
Would be nice to turn that into a macro define in inclue/asm so we can
get rid of that ugly #ifdef. Doing something like
_machine_type(<type>) that return 0 on a match and -1 for no match or
similar.
Jes
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-12 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 9:12 Mac/m68k patches? Geert Uytterhoeven
2000-12-12 10:50 ` Franz Sirl
2000-12-12 11:05 ` Geert Uytterhoeven
2000-12-12 11:25 ` Franz Sirl
2000-12-12 18:11 ` Jes Sorensen [this message]
[not found] <19341106051932.29140@192.168.1.2>
2000-12-12 12:28 ` Geert Uytterhoeven
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=d3bsuhldb0.fsf@lxplus015.cern.ch \
--to=jes@linuxcare.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--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 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.