All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alexandre Rostovtsev <tetromino@gmail.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lenovo-sl-laptop : driver for review
Date: Fri, 20 Feb 2009 00:00:33 -0300	[thread overview]
Message-ID: <20090220030033.GA18425@khazad-dum.debian.net> (raw)
In-Reply-To: <20090216151809.GA4724@srcf.ucam.org>

On Mon, 16 Feb 2009, Matthew Garrett wrote:
> On Mon, Feb 16, 2009 at 02:59:18AM -0500, Alexandre Rostovtsev wrote:
> > +static struct device_attribute dev_attr_bluetooth_enable =
> > +	__ATTR(bluetooth_enable, S_IWUSR | S_IRUGO,
> > +		bluetooth_enable_show, bluetooth_enable_store);
> 
> You support rfkill, so I'm not sure there's a benefit in exposing the 
> same functionality via a custom sysfs node.

Not only there is no benefit, it won't work at all.  The rfkill core will
set the radio state to match the global state for that radio type during the
rfkill_register() call.

Alexandre,  if the thinkpad-sl can store rfkill state across shutdown in
nvram or something like that, there is an API on the rfkill core that you
can use.  The current thinkpad-acpi code does it, you can use that as an
example.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-02-20  3:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  7:59 [PATCH] lenovo-sl-laptop : driver for review Alexandre Rostovtsev
2009-02-16 15:18 ` Matthew Garrett
2009-02-20  3:00   ` Henrique de Moraes Holschuh [this message]
2009-02-16 15:21 ` Matthew Garrett
2009-02-27 13:27 ` Pavel Machek
2009-02-28 14:37   ` Henrique de Moraes Holschuh
2009-03-10 11:22     ` Pavel Machek
2009-03-10 11:34       ` Henrique de Moraes Holschuh
2009-03-10 14:12         ` Pavel Machek

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=20090220030033.GA18425@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=tetromino@gmail.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 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.