From: Marcel Holtmann <marcel@holtmann.org>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-input@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] rfkill: Add support for KEY_RFKILL
Date: Fri, 13 Nov 2009 06:33:57 +0100 [thread overview]
Message-ID: <1258090437.3299.4.camel@violet> (raw)
In-Reply-To: <1252603292-20830-2-git-send-email-mjg@redhat.com>
Hi Matthew,
> Add support for handling KEY_RFKILL in the rfkill input module. This
> simply toggles the state of all rfkill devices. The comment in rfkill.h
> is also updated to reflect that RFKILL_TYPE_ALL may be used inside the
> kernel.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
looks good and seems to got lost somehow.
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2009-11-13 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 17:21 [PATCH 1/2] input: Add KEY_RFKILL Matthew Garrett
[not found] ` <1252603292-20830-1-git-send-email-mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-09-10 17:21 ` [PATCH 2/2] rfkill: Add support for KEY_RFKILL Matthew Garrett
2009-11-13 5:33 ` Marcel Holtmann [this message]
2009-09-10 17:27 ` [PATCH 1/2] input: Add KEY_RFKILL Luis R. Rodriguez
[not found] ` <43e72e890909101027saf1ed35u23936729eccf3f92-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-10 17:31 ` Matthew Garrett
2009-09-11 5:13 ` Dmitry Torokhov
[not found] ` <20090911051259.GC23210-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2009-11-13 5:34 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2010-02-16 21:36 Matthew Garrett
[not found] ` <1266356185-10324-1-git-send-email-mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-16 21:36 ` [PATCH 2/2] rfkill: Add support for KEY_RFKILL Matthew Garrett
2010-02-16 23:04 ` Marcel Holtmann
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=1258090437.3299.4.camel@violet \
--to=marcel@holtmann.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
/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 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).