linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Carlos Corbacho <cathectic@gmail.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] input: Add wireless and bluetooth keycodes
Date: Thu, 3 May 2007 07:58:45 -0400	[thread overview]
Message-ID: <d120d5000705030458m7909bc5enc2ff6621f542c7cf@mail.gmail.com> (raw)
In-Reply-To: <200705031215.16971.cathectic@gmail.com>

Hi Carlos,

On 5/3/07, Carlos Corbacho <cathectic@gmail.com> wrote:
> Add wireless and bluetooth keycodes.

Already have them:

#define KEY_BLUETOOTH           237
#define KEY_WLAN                238

> Also, add keycodes for these
> keys having a separate off state (This is true on some machines,
> such as many Acer laptops).
>

Not sure why this is needed.

-- 
Dmitry

  reply	other threads:[~2007-05-03 11:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 11:15 [PATCH] input: Add wireless and bluetooth keycodes Carlos Corbacho
2007-05-03 11:58 ` Dmitry Torokhov [this message]
2007-05-03 12:18   ` Carlos Corbacho

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=d120d5000705030458m7909bc5enc2ff6621f542c7cf@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=cathectic@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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).