public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Alex Hung <alex.hung@canonical.com>
Cc: Darren Hart <dvhart@infradead.org>,
	Corentin Chary <corentin.chary@gmail.com>,
	"platform-driver-x86@vger.kernel.org" 
	<platform-driver-x86@vger.kernel.org>,
	acpi4asus-user@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2] asus-rbtn: new driver for asus radio button for Windows 8
Date: Fri, 3 Jul 2015 09:25:23 +0200	[thread overview]
Message-ID: <20150703072523.GB1841@pali> (raw)
In-Reply-To: <CAJ=jquaDCaGv8PXuib7CFZAWUCTCZhkju0RZn-6v4MRCJhfgkA@mail.gmail.com>

On Thursday 02 July 2015 15:10:39 Alex Hung wrote:
> Thanks for the support.  I will create v3 based with LED triggers.
> 
> Just for information.  ASUS's wording is as below:
> 
> Fn+F2 can be used to turn on or off all radio capabilities in the
> device (as known as airplane mode switch).  I don't have any
> preferences on the name.  We may use the term airplane-mode do if
> asus-rbtn is not preferred.  Let me know if there are any suggestions.
> 

This is OK, but I though that ACPI ATK4001 device is some
multifunctional device, which is doing more then LED control... (At
least I understand it from your comments). So in this case I would not
call driver led/radio related. Right?

> 
> On Wed, Jul 1, 2015 at 7:48 PM, Pali Rohár <pali.rohar@gmail.com> wrote:
> > On Wednesday 01 July 2015 00:09:41 Alex Hung wrote:
> >> ATK4001 is an independent ACPI device, and Method(HSWC) is its method
> >> to control LED (actually it has other functions but only LED is needed
> >> so far).
> >
> > If this driver is for supporting ACPI ATK4001 device (which has couple
> > of methods, not only LED) it is really good idea to name it asus-rbtn?
> >
> > Darren, you as maintainer of platform drivers, what do you think? I
> > believe in future this driver will be extended to support more functions
> > and so name asus-rbtn will be confusing.
> >
> > --
> > Pali Rohár
> > pali.rohar@gmail.com
> 

-- 
Pali Rohár
pali.rohar@gmail.com

  reply	other threads:[~2015-07-03  7:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  2:57 [PATCH][v2] asus-rbtn: new driver for asus radio button for Windows 8 Alex Hung
2015-06-25  4:04 ` Darren Hart
2015-06-25  6:58 ` Paul Bolle
2015-06-25 20:00   ` Darren Hart
2015-06-26 14:56 ` Pali Rohár
2015-06-26 15:24   ` Alex Hung
2015-06-29 12:29     ` Pali Rohár
2015-06-30  8:38       ` Alex Hung
2015-06-30  8:58         ` Pali Rohár
2015-06-30 16:09           ` Alex Hung
2015-06-30 17:04             ` Pali Rohár
2015-07-01 11:48             ` Pali Rohár
2015-07-02  7:10               ` Alex Hung
2015-07-03  7:25                 ` Pali Rohár [this message]
2015-07-06  1:35                   ` Alex Hung
2015-07-06 22:43                     ` Darren Hart
2015-07-07 14:25                       ` Pali Rohár
2015-07-09 20:52                         ` Darren Hart
2015-07-10  1:52                           ` Alex Hung
2015-07-12 13:02                             ` Corentin Chary
2015-06-30 16:17       ` Darren Hart

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=20150703072523.GB1841@pali \
    --to=pali.rohar@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=alex.hung@canonical.com \
    --cc=corentin.chary@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox