From: Corentin CHARY <corentincj@iksaif.net>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, acpi4asus-user@lists.sourceforge.net
Subject: Re: [patch 0/7] New misc/asus-laptop.c driver
Date: Tue, 30 Jan 2007 09:28:53 +0100 [thread overview]
Message-ID: <200701300928.53852.corentincj@iksaif.net> (raw)
In-Reply-To: <200701300253.25321.lenb@kernel.org>
>
> 1-7 applied to acpi-test
> I also ran scripts/Lindent over it to fix the whitespace.
> Then, after merging into acpi-test I also applied the patch below.
>
> Your choice if you want to make future updates with incremental patches
> on top of acpi-test or re-send the series.
incremental patches on top of acpi-test are fine :)
> Also, while I see that distros do set CONFIG_LEDS_CLASS,
> depending on it will make the driver vanish from menuconfig
> if somebody hasn't set it. I don't know if this is a big deal or not.
> One possibility is to not depend on it in Kconfig, but via #ifdef's in the
> source. The other is to retreat to using select -- which I'm hopeful we can
> avoid. Or, maybe folks that don't get the driver via distro (who tend to
> enable everything) will not get stumped by this.
As the old asus_acpi doesn't work on new models, and still buggy, I think
distros will enable asus-laptop (and LED/BACKLIGHT) by default ... Those that
don't get the driver via distro will find it if they search (as the name
asus-laptop is accepted, I will post a warning on acpi4asus.sf.net, to say
that the driver have a new name, etc ...).
Thanks =)
> thanks
> -Len
--
CHARY 'Iksaif' Corentin
http://xf.iksaif.net
prev parent reply other threads:[~2007-01-30 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:54 [patch 0/7] New misc/asus-laptop.c driver Corentin CHARY
2007-01-26 7:51 ` Len Brown
2007-01-26 13:04 ` Corentin CHARY
2007-01-30 7:53 ` Len Brown
2007-01-30 8:28 ` Corentin CHARY [this message]
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=200701300928.53852.corentincj@iksaif.net \
--to=corentincj@iksaif.net \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=lenb@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox