All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ibm-acpi-devel@lists.sourceforge.net, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 6/7] ACPI: thinkpad-acpi: dequeue all pending hot key events at once
Date: Sun, 23 Sep 2007 22:33:09 -0400	[thread overview]
Message-ID: <200709232233.10049.lenb@kernel.org> (raw)
In-Reply-To: <20070921135340.GA11125@khazad-dum.debian.net>

On Friday 21 September 2007 09:53, Henrique de Moraes Holschuh wrote:
> On Thu, 20 Sep 2007, Len Brown wrote:
> > On Thursday 20 September 2007 09:50, Henrique de Moraes Holschuh wrote:
> > > Receive all pending hot key events at once from a single notification, and
> > > don't complain if the queue is empty.
> 
> Maybe I should have s/hot.?key/HKEY/ throughout this patch.
> 
> The HKEY handler is the thinkpad-specific handler to message-pass
> interesting events to the O.S. This include hot key pressing, but also
> inclures: LID open/close, radio switch toggling, what looks like thermal
> alarms, reason for wakeup (bay eject, whatever), notification of impending
> undock (to show a helper to the user explaining how to undock a x40/x60,
> etc)... and only IBM and Lenovo knows what else.  Hot key presses are just
> one of the many things reported through thinkpad HKEY events.
> 
> > If this is really an event due to an hotkey (emphasis on the word KEY:-),
> > why is it being sent via netlink instead of via input?
> 
> Like I said, if it hit that branch, it is some other notification than a hot
> key press :-)  Yeah, it is non-obvious.
> 
> I will rework the patch to use the word HKEY event instead of hotkey event
> where applicable.

Thanks for the clarification, Henrique.

  reply	other threads:[~2007-09-24  2:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-20 13:50 [GIT PATCH] thinkpad-acpi changes for the merge window (part 1) Henrique de Moraes Holschuh
2007-09-20 13:50 ` [PATCH 1/7] ACPI: thinkpad-acpi: make room for more features in tp_features bitfield Henrique de Moraes Holschuh
2007-09-20 13:50 ` [PATCH 2/7] ACPI: thinkpad-acpi: issue EV_SYNC after EV_SWITCH Henrique de Moraes Holschuh
2007-09-20 13:50 ` [PATCH 3/7] ACPI: thinkpad-acpi: add mutex-based locking to input device event send path Henrique de Moraes Holschuh
     [not found] ` <11902962603691-git-send-email-hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-09-20 13:50   ` [PATCH 4/7] ACPI: thinkpad-acpi: keep track of module state Henrique de Moraes Holschuh
2007-09-20 13:50   ` [PATCH 5/7] ACPI: thinkpad-acpi: check version of hot key firmware Henrique de Moraes Holschuh
2007-09-20 13:50   ` [PATCH 6/7] ACPI: thinkpad-acpi: dequeue all pending hot key events at once Henrique de Moraes Holschuh
     [not found]     ` <11902962613565-git-send-email-hmh-N3TV7GIv+o9fyO9Q7EP/yw@public.gmane.org>
2007-09-21  0:42       ` Len Brown
     [not found]         ` <200709202042.22724.lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2007-09-21 13:53           ` Henrique de Moraes Holschuh
2007-09-24  2:33             ` Len Brown [this message]
2007-09-20 13:51 ` [PATCH 7/7] ACPI: thinkpad-acpi: fix regression on HKEY LID event handling 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=200709232233.10049.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=hmh@hmh.eng.br \
    --cc=ibm-acpi-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.