| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 20 Sep 2009 08:16:56 -0300 From: Henrique de Moraes Holschuh <hmh@....eng.br> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, rpurdie@...ys.net, lenb@...nel.org, rui.zhang@...el.com, corentincj@...aif.net Subject: Re: [PATCH 1/3] backlight: Allow drivers to update the core, and generate events on changes On Sun, 20 Sep 2009, Matthew Garrett wrote: > On Sat, Sep 19, 2009 at 08:24:24PM -0300, Henrique de Moraes Holschuh wrote: > > Should the driver notify of *any* changes, even when the user is hitting the > > "ceiling" or the "floor" and the backlight value didn't really change? > > I'd say yes - the user will expect the UI to appear whenever they hit > the button. Ok. The thinkpad-acpi changes depends on a large patchset that I should send to Len today. After that, I will send the patch that adds brightness event support. Are you backlight patches in any tree? Are them expected to hit mainline this merge window? -- "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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists