From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Asus atk0110 driver
Date: Mon, 23 Jun 2008 13:48:53 +0000 [thread overview]
Message-ID: <20080623154853.09e4d327@hyperion.delvare> (raw)
In-Reply-To: <20080618212629.GA7917@dreamland.darkstar.lan>
On Mon, 23 Jun 2008 14:41:29 +0200, Gabriel C wrote:
> Jean Delvare wrote:
> > On Sun, 22 Jun 2008 18:15:51 +0200, Gabriel C wrote:
> >> Luca what do you think about creating a proper patch for the driver too and send it over to
> >> Greg to be included in his linux-staging tree ? I think that way it will get more testing.
> >
> > Don't know which Greg you're thinking of?
>
>
> Greg Kroah-Hartman
>
> >This is an ACPI-based
> > hardware monitoring driver, so it would go to either the ACPI folks or
> > (IMHO better) to the hwmon folks (i.e. the lm-sensors list). I agree
> > that having a proper patch would be nice (but I also want to say that I
> > will not have the time to review the driver myself.)
> >
>
>
> Yes sure but from what I understand linux-staging[1] tree holds not_yet__really_ready_to_merge
> drivers , filesystems and such. I don't think it does matter it is an ACPI driver.
>
> [1] http://lkml.org/lkml/2008/6/10/329
Ah, I didn't know about this new kernel tree, thanks for the pointer. I
get what you meant now.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-06-23 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 21:26 [lm-sensors] Asus atk0110 driver Luca Tettamanti
2008-06-19 7:16 ` Jean Delvare
2008-06-22 16:15 ` Gabriel C
2008-06-23 9:06 ` Jean Delvare
2008-06-23 12:41 ` Gabriel C
2008-06-23 13:48 ` Jean Delvare [this message]
2008-06-30 19:58 ` Luca Tettamanti
2008-06-30 22:20 ` Gabriel C
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=20080623154853.09e4d327@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@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 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.