LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: torvalds@osdl.org, linux-input@vger.kernel.org, dtor@mail.ru,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] keyboard notifier documentation
Date: Sat, 9 Feb 2008 15:43:41 +0000	[thread overview]
Message-ID: <20080209154341.GK4379@implementation> (raw)
In-Reply-To: <47ADC913.5010202@oracle.com>

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

  reply	other threads:[~2008-02-09 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-09  1:33 Samuel Thibault
2008-02-09  4:12 ` Randy Dunlap
2008-02-09 11:40   ` Samuel Thibault
2008-02-09 15:38     ` Randy Dunlap
2008-02-09 15:43       ` Samuel Thibault [this message]
2008-02-09 11:44 ` [PATCH2] " Samuel Thibault

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=20080209154341.GK4379@implementation \
    --to=samuel.thibault@ens-lyon.org \
    --cc=dtor@mail.ru \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@osdl.org \
    --subject='Re: [PATCH] keyboard notifier documentation' \
    /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

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).