From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Mac/m68k patches?
Date: Tue, 12 Dec 2000 11:50:14 +0100 [thread overview]
Message-ID: <00121211501400.01036@enzo.bigblue.local> (raw)
In-Reply-To: <Pine.GSO.4.10.10012121010320.1109-100000@escobaria.sonytel.be>
On Tuesday 12 December 2000 10:12, Geert Uytterhoeven wrote:
> Hi,
>
> I have these Mac/m68k patches in my patchqueue which affect PowerMac as
> well. Anyone who has a problem with them, or can I send them to Linus?
>
> diff -urN linux-2.4.0-test12/drivers/input/keybdev.c
> linux-m68k-2.4.0-test12/drivers/input/keybdev.c ---
> linux-2.4.0-test12/drivers/input/keybdev.c Fri Jul 28 03:36:54 2000 +++
> linux-m68k-2.4.0-test12/drivers/input/keybdev.c Tue Dec 12 09:02:47 2000 @@
> -90,7 +90,7 @@
> return 0;
> }
>
> -#elif defined(CONFIG_ADB_KEYBOARD)
> +#elif defined(CONFIG_INPUT_ADBHID)
>
> static unsigned char mac_keycodes[128] =
> { 0, 53, 18, 19, 20, 21, 23, 22, 26, 28, 25, 29, 27, 24, 51, 48,
This one is wrong, the right patch is in bk_2_3 and has been feeded to Linus
already, see my post on l-k last week. You can however trigger Linus again to
finally apply it :-). The patch to adbhid.c is fine with me.
I can't talk about the rest of the patch though.
Franz.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-12 10:50 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 [this message]
2000-12-12 11:05 ` Geert Uytterhoeven
2000-12-12 11:25 ` Franz Sirl
2000-12-12 18:11 ` Jes Sorensen
[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=00121211501400.01036@enzo.bigblue.local \
--to=franz.sirl-kernel@lauterbach.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 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).