From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: linux-acpi@vger.kernel.org, lenb@kernel.org, nokos@gmx.net
Subject: Re: [PATCH] Fujitsu-laptop update
Date: Wed, 28 May 2008 10:04:02 +0100 [thread overview]
Message-ID: <20080528090402.GA29533@srcf.ucam.org> (raw)
In-Reply-To: <200805280412.m4S4C6Cr008232@turbo.physics.adelaide.edu.au>
On Wed, May 28, 2008 at 01:42:06PM +0930, Jonathan Woithe wrote:
> At the risk of sounding uninformed (which is fine, because I am :-) ), how
> does one go about finding the appropriate ID for the PNP device? Are we
> talking the FUJ02B1 and FUJ02E3 devices themselves (in which case we'll have
> two such modaliases) or some other overarching device?
Yup, those sound appropriate.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2008-05-28 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 0:05 [PATCH] Fujitsu-laptop update Jonathan Woithe
2008-05-23 12:22 ` Richard Hughes
2008-05-23 16:16 ` Matthew Garrett
2008-05-28 4:12 ` Jonathan Woithe
2008-05-28 9:04 ` Matthew Garrett [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=20080528090402.GA29533@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=nokos@gmx.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