linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: mberglund <matt@realestatesafari.com>,
	<linuxppc-dev@lists.linuxppc.org>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: Kernel compile errors in latest snap
Date: Fri, 18 Aug 2000 11:41:45 +0200	[thread overview]
Message-ID: <20000818094145.16616@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0008180131200.1723-100000@europa.rcinfo.net>


>[root@ linuxppc_2_3]# grep -r input_keycode drivers
>drivers/macintosh/mac_keyb.c:static void input_keycode(int, int);
>drivers/macintosh/mac_keyb.c:   input_keycode(data[1], 0);
>drivers/macintosh/mac_keyb.c:           input_keycode(data[2], 0);
>drivers/macintosh/mac_keyb.c:input_keycode(int keycode, int repeat)
>drivers/macintosh/mac_keyb.c:   input_keycode(last_keycode, 1);
>drivers/input/adbhid.c:static void adbhid_input_keycode(int, int, int);
>drivers/input/adbhid.c: input_keycode(id, data[1], 0);
>drivers/input/adbhid.c:         input_keycode(id, data[2], 0);
>drivers/input/adbhid.c:adbhid_input_keycode(int id, int keycode, int
>repeat)

In drivers/input/adbhid.c, replace input_keycode by adbhid_input_keycode.
I though I pushed this fix before I left, but since I had some problems
with bk, it may still be pending in my local tree. I'll fix all that this
week-end (maybe tonight).

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2000-08-18  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-18  5:33 Kernel compile errors in latest snap mberglund
2000-08-18  9:24 ` Martin Costabel
2000-08-18  9:41 ` Benjamin Herrenschmidt [this message]

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=20000818094145.16616@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=matt@realestatesafari.com \
    /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).