linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org, dtor@mail.ru,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] Console keyboard events and accessibility
Date: Tue, 21 Aug 2007 13:02:33 -0700	[thread overview]
Message-ID: <20070821130233.58faaa8a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070821005718.GD3658@interface.famille.thibault.fr>

On Tue, 21 Aug 2007 02:57:18 +0200
Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:

> Some external modules like Speakup need to use the PC keyboard to control
> them and also need to get keyboard feedback (caps lock status, etc.)
> 
> This adds a keyboard notifier that such modules can use to get the keyboard
> events and possibly eat them, at several stages:

Adding hooks for non-merged modules is considered sinful.  Making these new
exports EXPORT_SYMBOL_GPL might ease the pain.

Is there any prospect of getting at least one of these "external modules
like Speakup" merged into mainline?

  reply	other threads:[~2007-08-21 20:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21  0:57 [PATCH] Console keyboard events and accessibility Samuel Thibault
2007-08-21 20:02 ` Andrew Morton [this message]
2007-08-21 20:22   ` Samuel Thibault
2007-08-25  1:07     ` Adrian Bunk
2007-08-27 14:59       ` Samuel Thibault
2007-08-21 20:42 ` Jan Engelhardt
2007-08-21 20:49   ` Samuel Thibault
2007-07-12 19:19     ` Pavel Machek
2007-09-01 12:26       ` Samuel Thibault
2007-09-01 12:32         ` Pavel Machek
2007-09-01 12:51           ` Samuel Thibault
2007-09-01 17:23             ` Pavel Machek
2007-09-01 17:33               ` Samuel Thibault
2007-09-01 18:18                 ` Pavel Machek
2007-09-01 19:36                   ` Samuel Thibault

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=20070821130233.58faaa8a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dtor@mail.ru \
    --cc=jkosina@suse.cz \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.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).