From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Daniel Mack <daniel@caiaq.de>,
Eric Piel <eric.piel@tremplin-utc.net>,
kernel list <linux-kernel@vger.kernel.org>,
Vladimir Botka <vbotka@suse.cz>,
mmarek@suse.cz
Subject: Re: hp_accel: add two more axis information
Date: Mon, 23 Mar 2009 11:07:00 +0100 [thread overview]
Message-ID: <20090323100659.GA17681@elf.ucw.cz> (raw)
In-Reply-To: <20090322171128.26c790bb.akpm@linux-foundation.org>
On Sun 2009-03-22 17:11:28, Andrew Morton wrote:
> On Sun, 8 Mar 2009 22:07:57 +0100 Pavel Machek <pavel@ucw.cz> wrote:
>
> > On Sun 2009-03-08 22:06:25, Daniel Mack wrote:
> > > On Sun, Mar 08, 2009 at 10:03:30PM +0100, Pavel Machek wrote:
> > > > Add two more laptops to whitelist.
> > > >
> > > > Signed-off-by: Michal Marek <mmarek@suse.cz>
> > > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > > >
> > > >
> > > > diff --git a/drivers/hwmon/hp_accel.c b/drivers/hwmon/hp_accel.c
> > > > index 29c83b5..448a462 100644
> > > > --- a/drivers/hwmon/hp_accel.c
> > > > +++ b/drivers/hwmon/hp_accel.c
> > > > @@ -187,6 +187,7 @@ static struct dmi_system_id lis3lv02d_dmi_ids[] = {
> > > > AXIS_DMI_MATCH("NC2510", "HP Compaq 2510", y_inverted),
> > > > AXIS_DMI_MATCH("NC8510", "HP Compaq 8510", xy_swap_inverted),
> > > > AXIS_DMI_MATCH("HP2133", "HP 2133", xy_rotated_left),
> > > > + AXIS_DMI_MATCH("HP2140", "HP 2140", xy_swap_inverted),
> > > > AXIS_DMI_MATCH("NC653x", "HP Compaq 653", xy_rotated_left_usd),
> > > > AXIS_DMI_MATCH("NC673x", "HP Compaq 673", xy_rotated_left_usd),
> > > > AXIS_DMI_MATCH("NC651xx", "HP Compaq 651", xy_rotated_right),
> > > > @@ -201,6 +202,7 @@ static struct dmi_system_id lis3lv02d_dmi_ids[] = {
> > > > PRODUCT_NAME, "HP Pavilion dv5",
> > > > BOARD_NAME, "3600",
> > > > y_inverted),
> > > > + AXIS_DMI_MATCH("DV7", "HP Pavilion dv7", x_inverted),
> > > > { NULL, }
> > > > /* Laptop models without axis info (yet):
> > > > * "NC6910" "HP Compaq 6910"
> > >
> > > Does this apply on top of my recent ACPI resolve patches? Could you test
> > > the latest versions already?
> >
> > I guess it should; you did not change anything in the
> > whitelist. Unfortunately, I no longer have hardware to do testing.
>
> I'm all confused and don't know what to do with this patch.
>
> I guess I'll just apply it and see if I get shouted at.
That sounds like a plan :-). And I don't think you'll get shouted at,
the patch should be very safe.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-03-23 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 21:03 hp_accel: add two more axis information Pavel Machek
2009-03-08 21:06 ` Daniel Mack
2009-03-08 21:07 ` Pavel Machek
2009-03-23 0:11 ` Andrew Morton
2009-03-23 10:07 ` Pavel Machek [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=20090323100659.GA17681@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=daniel@caiaq.de \
--cc=eric.piel@tremplin-utc.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=vbotka@suse.cz \
/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