From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
Cc: linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH 1/2] input: Add KEY_RFKILL_ALL
Date: Sat, 1 Aug 2009 23:25:37 +0100 [thread overview]
Message-ID: <20090801222537.GA24262@srcf.ucam.org> (raw)
In-Reply-To: <1249164685.3491.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
On Sat, Aug 01, 2009 at 03:11:25PM -0700, Marcel Holtmann wrote:
> and that is what it should NOT imply. The policy if it applies to all
> internal devices, all devices in general or just WiFi or Bluetooth for
> example is up to the user.
>
> We are NOT going to have any kind of RFKILL policy in the kernel in the
> future. We will remove rfkill-input once we have a proper userspace
> solution (aka rfkilld or similar).
We seem to be talking at cross purposes here. My objection to the name
KEY_RFKILL is that it gives no indication what it's meant to be or why
it's different to KEY_WLAN. KEY_RFKILL implies that it's the only input
component that an rfkill policy agent needs to listen to, which isn't
the case.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-input@vger.kernel.org, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH 1/2] input: Add KEY_RFKILL_ALL
Date: Sat, 1 Aug 2009 23:25:37 +0100 [thread overview]
Message-ID: <20090801222537.GA24262@srcf.ucam.org> (raw)
In-Reply-To: <1249164685.3491.28.camel@localhost.localdomain>
On Sat, Aug 01, 2009 at 03:11:25PM -0700, Marcel Holtmann wrote:
> and that is what it should NOT imply. The policy if it applies to all
> internal devices, all devices in general or just WiFi or Bluetooth for
> example is up to the user.
>
> We are NOT going to have any kind of RFKILL policy in the kernel in the
> future. We will remove rfkill-input once we have a proper userspace
> solution (aka rfkilld or similar).
We seem to be talking at cross purposes here. My objection to the name
KEY_RFKILL is that it gives no indication what it's meant to be or why
it's different to KEY_WLAN. KEY_RFKILL implies that it's the only input
component that an rfkill policy agent needs to listen to, which isn't
the case.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-08-01 22:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 18:54 [PATCH 1/2] input: Add KEY_RFKILL_ALL Matthew Garrett
2009-08-01 18:54 ` Matthew Garrett
[not found] ` <1249152859-14769-1-git-send-email-mjg-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-08-01 18:54 ` [PATCH 2/2] rfkill: Add support for KEY_RFKILL_ALL Matthew Garrett
2009-08-01 18:54 ` Matthew Garrett
2009-08-01 20:25 ` Bastien Nocera
2009-08-01 20:41 ` Marcel Holtmann
2009-08-01 20:38 ` [PATCH 1/2] input: Add KEY_RFKILL_ALL Marcel Holtmann
2009-08-01 20:45 ` Matthew Garrett
2009-08-01 20:52 ` Marcel Holtmann
2009-08-01 20:54 ` Matthew Garrett
[not found] ` <20090801205445.GA23751-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-08-01 21:48 ` Marcel Holtmann
2009-08-01 21:48 ` Marcel Holtmann
[not found] ` <1249163327.3491.24.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-08-01 21:51 ` Matthew Garrett
2009-08-01 21:51 ` Matthew Garrett
[not found] ` <20090801215130.GA24201-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2009-08-01 22:11 ` Marcel Holtmann
2009-08-01 22:11 ` Marcel Holtmann
[not found] ` <1249164685.3491.28.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-08-01 22:25 ` Matthew Garrett [this message]
2009-08-01 22:25 ` Matthew Garrett
2009-08-02 7:55 ` Johannes Berg
2009-08-02 1:05 ` Henrique de Moraes Holschuh
2009-08-02 1:15 ` Matthew Garrett
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=20090801222537.GA24262@srcf.ucam.org \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.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.