From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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: Mon, 27 Aug 2007 16:59:12 +0200 [thread overview]
Message-ID: <20070827145912.GB3268@implementation.ifsic.univ-rennes1.fr> (raw)
In-Reply-To: <20070825010704.GK30705@stusta.de>
Hi,
Adrian Bunk, le Sat 25 Aug 2007 03:07:04 +0200, a écrit :
> > If they
> > remain in -mm for some time and people don't complain, well that's good
> > too: at least we know how speakup may hook into the kernel when it gets
> > merged.
> >...
>
> Without any users it's dead code noone uses,
Not so much dead: the notify chain will get called anyway, taking
spinlocks, etc. even if nothing is really called. And people can see
the patches and complain if they think they're bad.
> BTW: Are these the speakup patches that were in -ac five years ago?
No, they are some rework of the way Speakup glues into the kernel.
Samuel
next prev parent reply other threads:[~2007-08-27 14:59 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
2007-08-21 20:22 ` Samuel Thibault
2007-08-25 1:07 ` Adrian Bunk
2007-08-27 14:59 ` Samuel Thibault [this message]
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=20070827145912.GB3268@implementation.ifsic.univ-rennes1.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=dtor@mail.ru \
--cc=jkosina@suse.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--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;
as well as URLs for NNTP newsgroup(s).