linux-kernel - Re: [PATCH 8/9] Input: Block suspend while event queue is not empty.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <v2sd6200be21004232158m3a3eaebai1ca0e49ae79e97f@mail.gmail.com>
Date:	Fri, 23 Apr 2010 21:58:56 -0700
From:	Arve Hjønnevåg <arve@...roid.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Thadeu Lima de Souza Cascardo <cascardo@...oscopio.com>,
	Márton Németh <nm127@...email.hu>,
	Sven Neumann <s.neumann@...mfeld.com>,
	Tero Saarni <tero.saarni@...il.com>,
	Henrik Rydberg <rydberg@...omail.se>,
	Matthew Garrett <mjg@...hat.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org
Subject: Re: [PATCH 8/9] Input: Block suspend while event queue is not empty.

2010/4/23 Randy Dunlap <randy.dunlap@...cle.com>:
> On Thu, 22 Apr 2010 18:08:57 -0700 Arve Hjønnevåg wrote:
>
>> Add an ioctl, EVIOCSSUSPENDBLOCK, to enable a suspend_blocker that will block
>> suspend while the event queue is not empty. This allows userspace code to
>> process input events while the device appears to be asleep.
>
>
> All new ioctls need to be added to Documentation/ioctl/ioctl-number.txt, please.
>

These two appear to already be covered by "'E'     all
linux/input.h           conflict!", but I will add a line the user
space suspend blocker ioctls added earlier in this patch set.

-- 
Arve Hjønnevåg
--
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/