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:32:11 +0200 [thread overview]
Message-ID: <200704112032.11772.dkukawka@suse.de> (raw)
In-Reply-To: <200704112018.31026.dkukawka@suse.de>
On Mittwoch, 11. April 2007, Danny Kukawka wrote:
> 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.
Btw. looks as if a new version of the driver (v0.41) is already in the mm-tree.
Danny
next prev parent reply other threads:[~2007-04-11 18:33 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
2007-04-11 18:32 ` Danny Kukawka [this message]
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=200704112032.11772.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