From: Danny Kukawka <dkukawka@suse.de>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net, corentincj@iksaif.net,
sziwan@users.sourceforge.net
Subject: Re: [PATCH 1/1] ACPI: asus_acpi, support F2JE model
Date: Wed, 11 Apr 2007 20:18:30 +0200 [thread overview]
Message-ID: <200704112018.31026.dkukawka@suse.de> (raw)
In-Reply-To: 461CE6AA.6050806@gmail.com
Jiri Slaby wrote:
> Corentin CHARY napsal(a):
>> Le Wednesday 11 April 2007 11:33:48 Jiri Slaby, vous avez écrit :
>>> asus_acpi, support F2JE model
>> Just use the new asus-laptop driver =)
>> (see acpi4asus-0.40)
>
> code seems good, but this is not so good:
> #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,20)
> #warning "This module does not support 2.6.20 yet, wait for a new release
> #=)" endif
>
> When do you plan to support latest kernels and merge it to mainline?
This patch fixes acpi4asus-0.40 for me at least with 2.6.20 on a ASUS R1F.
Danny
Signed-off-by: Danny Kukawka <dkukawka@suse.de>
---
asus-laptop.c | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
--- acpi4asus-0.40/driver/asus-laptop.c 2007-02-13 17:42:51.000000000 +0100
+++ acpi4asus-0.40/driver/asus-laptop.c 2007-04-11 20:12:49.000000000 +0200
@@ -41,8 +41,8 @@
# include <linux/autoconf.h>
#endif
-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,20)
-#warning "This module does not support 2.6.20 yet, wait for a new release =)"
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,21)
+#warning "This module does not support 2.6.21 yet, wait for a new release =)"
#endif
#include <linux/kernel.h>
@@ -226,8 +226,8 @@
static void object##_led_set(struct led_classdev *led_cdev, \
enum led_brightness value); \
static int object##_led_wk; \
- static void object##_led_update(void *data); \
- DECLARE_WORK(object##_led_work, object##_led_update, NULL); \
+ static void object##_led_update(struct work_struct *dummy); \
+ DECLARE_WORK(object##_led_work, object##_led_update); \
static struct led_classdev object##_led = { \
.name = "asus:" ledname, \
.brightness_set = object##_led_set, \
@@ -329,7 +329,7 @@
object##_led_wk = value; \
queue_work(led_workqueue, &object##_led_work); \
} \
- static void object##_led_update(void * data) \
+ static void object##_led_update(struct work_struct *dummy) \
{ \
int value = object##_led_wk; \
write_status(object##_set_handle, value, (mask)); \
@@ -1053,8 +1053,7 @@
struct backlight_device *bd;
if(brightness_set_handle && lcd_switch_handle) {
- bd = backlight_device_register (ASUS_HOTK_FILE, NULL,
- &asusbl_data);
+ bd = backlight_device_register (ASUS_HOTK_FILE, NULL, NULL, &asusbl_data);
if (IS_ERR (bd)) {
printk(ASUS_ERR
next prev parent reply other threads:[~2007-04-11 18:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 9:33 [PATCH 1/1] ACPI: asus_acpi, support F2JE model Jiri Slaby
2007-04-11 13:05 ` Corentin CHARY
2007-04-11 13:46 ` Jiri Slaby
2007-04-11 18:18 ` Danny Kukawka [this message]
2007-04-11 18:32 ` Danny Kukawka
2007-04-11 19:23 ` Jiri Slaby
2007-04-11 19:43 ` Danny Kukawka
2007-04-11 13:10 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2007-04-11 13:04 Jiri Slaby
2007-04-11 20:20 ` Andrew Morton
2007-04-11 20:32 ` Jiri Slaby
2007-04-11 20:37 ` Jiri Slaby
2007-04-11 21:06 ` Andrew Morton
2007-04-11 21:17 ` Jiri Slaby
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=200704112018.31026.dkukawka@suse.de \
--to=dkukawka@suse.de \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentincj@iksaif.net \
--cc=jirislaby@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sziwan@users.sourceforge.net \
/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