From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: Eric Cooper <ecc@cmu.edu>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI module for Asus Eee PC
Date: Sun, 27 Jan 2008 20:26:42 +0000 [thread overview]
Message-ID: <200801272026.43183.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <20080126144824.GD16281@stratocaster.home>
On Saturday 26 January 2008 14:48:24 Eric Cooper wrote:
> I happened to look at the patched asus_acpi.c module that was posted
> by Asus for the Eee PC and noticed that it's 75% dead code -- the Eee
> PC support is just stuck on at the end. And of course it conflicts
> with the real asus_acpi.ko in any kernel package.
>
> So I cleaned it up, renamed it eeepc_acpi, and packaged it as a
> separate out-of-kernel Debian package that can be built with
> module-assistant.
To submit a driver, it needs to be as a patch against the ACPI Git tree 'test'
branch.
New laptop drivers should:
1) Be in drivers/misc (asus_acpi is the only leftover in drivers/acpi -
everything else has already been moved, and no new laptop drivers will be
accepted in drivers/acpi)
2) proc is deprecated for new drivers - you should be using sysfs
3) #if LINUX_KERNEL_VERSION is an absolute no-no in upstream kernel code. Any
such instances should be stripped out of the code.
4) Patches should be run through scripts/checkpatch.pl, and new drivers
especially should be checkpatch clean - you will find it flags up quite a few
style problems with the code.
If you can address these and then resubmit a proper patch, then you will stand
a chance of getting this reviewed and accepted into the mainline kernel.
-Carlos
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
next prev parent reply other threads:[~2008-01-27 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 14:48 ACPI module for Asus Eee PC Eric Cooper
2008-01-27 20:26 ` Carlos Corbacho [this message]
2008-01-30 18:10 ` Corentin CHARY
2008-01-30 18:21 ` Eric Cooper
2008-01-30 21:27 ` Corentin CHARY
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=200801272026.43183.carlos@strangeworlds.co.uk \
--to=carlos@strangeworlds.co.uk \
--cc=ecc@cmu.edu \
--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