From: Clemens Schwaighofer <cs@tequila.co.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: [keyboard] current 2.6.1-bk6 yet not merged kbd.patch
Date: Wed, 21 Jan 2004 13:49:55 +0900 [thread overview]
Message-ID: <400E04F3.4070709@tequila.co.jp> (raw)
In-Reply-To: <200401210111.39050.murilo_pontes@yahoo.com.br>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Murilo Pontes wrote:
| I upgrade my 2.6.1 to 2.6.1-bk6,
|
| I found in diffview on kernel.org
|
-
------------------------------------------------------------------------------------
| drivers/input/keyboard/atkbd.c 10 + 28 -
0 !
| drivers/input/keyboard/maple_keyb.c 1 + 0 -
0 !
| drivers/input/keyboard/newtonkbd.c 2 + 0 -
0 !
|
-
-----------------------------------------------------------------------------------
|
| But attached patch yet not merged...... without this, abnt2
keyboard not work "/" and "?".
|
| Please merge this before 2.6.2 :)
yeah please. I don't want to redfine my sekey & X key definitines in
every kernel release. And I don't want to find more missing keys ...
*sob* *rant*
- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFADgTzjBz/yQjBxz8RArPfAJ9yqyAG9Ytcm8l3VDCrBNghLp144QCgqyBg
BXXFwpovXvNu9YEpdOIrX5Y=
=XS+6
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-01-21 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 1:11 [keyboard] current 2.6.1-bk6 yet not merged kbd.patch Murilo Pontes
2004-01-21 4:49 ` Clemens Schwaighofer [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=400E04F3.4070709@tequila.co.jp \
--to=cs@tequila.co.jp \
--cc=linux-kernel@vger.kernel.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