From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Carlos Garnacho <carlosg@gnome.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/5] hooking udev to SW_TABLET_MODE changes
Date: Mon, 16 Dec 2013 22:03:32 -0200 [thread overview]
Message-ID: <20131217000332.GA10466@khazad-dum.debian.net> (raw)
In-Reply-To: <1387234814-17716-1-git-send-email-carlosg@gnome.org>
On Tue, 17 Dec 2013, Carlos Garnacho wrote:
> The following patches make it possible to have udev/userspace notified when
> SW_TABLET_MODE changes on the switch device, without having to resort to
> poll()/select() for such sparse events. I've got udev patches locally to
> complement this.
I don't like this. We moved away from uevents for this kind of stuff (in
the general sense) because they, to put it lightly, are NOT appropriate for
input-event-like events.
Moving any sort of input event back to uevents is something I do NOT want to
support, ever. Any userspace that wants it for backwards compatibility can,
and DOES synthesize uevents from input events.
So, can you make a very strong case for this uevent?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2013-12-17 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 23:00 [PATCH 0/5] hooking udev to SW_TABLET_MODE changes Carlos Garnacho
2013-12-16 23:00 ` [PATCH 1/5] thinkpad_acpi: Send uevent when " Carlos Garnacho
2013-12-16 23:00 ` [PATCH 2/5] hp-wmi: " Carlos Garnacho
2013-12-16 23:00 ` [PATCH 3/5] xo15-ebook: " Carlos Garnacho
2013-12-16 23:00 ` [PATCH 4/5] classmate-laptop: " Carlos Garnacho
2013-12-16 23:00 ` [PATCH 5/5] fujitsu-tablet: " Carlos Garnacho
2013-12-17 0:03 ` Henrique de Moraes Holschuh [this message]
2013-12-17 12:06 ` [PATCH 0/5] hooking udev to " Carlos Garnacho
2013-12-17 19:16 ` Henrique de Moraes Holschuh
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=20131217000332.GA10466@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=carlosg@gnome.org \
--cc=linux-acpi@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