From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [RFC] rfkill/rfkill-input userspace API
Date: Sat, 28 Mar 2009 15:22:26 +0000 [thread overview]
Message-ID: <20090328152226.GA28425@srcf.ucam.org> (raw)
In-Reply-To: <20090328151416.GA8437@khazad-dum.debian.net>
On Sat, Mar 28, 2009 at 12:14:16PM -0300, Henrique de Moraes Holschuh wrote:
> What version of the X server does this? This kind of thing will
> probably need to end up in the rfkill-input docs :-(
1.5.3 or later, but any distribution running an earlier 1.5 should
really cherry-pick it back - a lot gets broken otherwise.
d936a4235c9625bd41569cef3452dd086284e0d7 is the commit. Pre-1.5 servers
shouldn't be using evdev so won't have this problem.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2009-03-28 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 15:58 [RFC] rfkill/rfkill-input userspace API Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 1/4] rfkill: prepare to export global states to userspace Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 2/4] rfkill: expose global switches through sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 3/4] rfkill: expose global state to sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 4/4] rfkill: export events for global state changes Henrique de Moraes Holschuh
2009-03-27 21:34 ` [RFC] rfkill/rfkill-input userspace API Johannes Berg
2009-03-28 12:37 ` Henrique de Moraes Holschuh
2009-03-27 22:11 ` Matthew Garrett
2009-03-28 12:36 ` Henrique de Moraes Holschuh
2009-03-28 12:44 ` Matthew Garrett
2009-03-28 12:47 ` Henrique de Moraes Holschuh
2009-03-28 12:53 ` Matthew Garrett
2009-03-28 14:48 ` Henrique de Moraes Holschuh
2009-03-28 15:02 ` Matthew Garrett
2009-03-28 15:14 ` Henrique de Moraes Holschuh
2009-03-28 15:22 ` Matthew Garrett [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=20090328152226.GA28425@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@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).