linux-kernel - Re: [PATCH] keyboard notifier documentation

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] [day] [month] [year] [list]

Message-ID: <20080209154341.GK4379@implementation>
Date:	Sat, 9 Feb 2008 15:43:41 +0000
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	torvalds@...l.org, linux-input@...r.kernel.org, dtor@...l.ru,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] keyboard notifier documentation

Randy Dunlap, le Sat 09 Feb 2008 07:38:59 -0800, a écrit :
> Samuel Thibault wrote:
> >Randy Dunlap, le Fri 08 Feb 2008 20:12:53 -0800, a écrit :
> >>On Sat, 9 Feb 2008 01:33:22 +0000 Samuel Thibault wrote:
> >>>+- 'vc' always provide the VC for which the keyboard event applies ;
> >>>+- 'down' is 1 for a key press event, 0 for a key release ;
> >>>+- 'shift' is the current modifier state, mask bit indexes are KG_* ;
> >>No space before the ';' (3 times).
> >
> >Well, as expected in French...  I'll fix that.
> >
> >>>+For each kind of event but the last, the callback may return 
> >>>NOTIFY_STOP in
> >>>+order to "eat" the event: the notify loop is stopped and the keyboard 
> >>>event is
> >>>+dropped.
> >>>+
> >>>+I a rough C snippet, we have:
> >>   In a rough (?)
> >
> >Yes, rough as "something that a C compiler will never accept, but that
> >you, human, will make sense out of it".
> 
> so s/I/In/ please.

Ah oops, sorry misunderstood what you raised, I actually had fixed it in
the second version.

Thanks,
Samuel
--
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/