From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>, Greg KH <greg@kroah.com>,
Richard Purdie <rpurdie@rpsys.net>,
Matthew Wilcox <matthew@wil.cx>, Len Brown <lenb@kernel.org>,
"Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Subject: Re: [RFC PATCH V2 2/2] introduce ACPI ALS device driver
Date: Thu, 06 Aug 2009 10:50:58 -0600 [thread overview]
Message-ID: <1249577458.457.40.camel@dc7800.home> (raw)
In-Reply-To: <1249571361.457.21.camel@dc7800.home>
On Thu, 2009-08-06 at 09:09 -0600, Bjorn Helgaas wrote:
> > + status = acpi_get_name(als->device->handle, ACPI_FULL_PATHNAME, &name);
> > + if (ACPI_FAILURE(status)) {
> > + result = -ENODEV;
> > + goto end;
> > + }
> > +
> > + als->als_sys = als_device_register(&acpi_als_ops, name.pointer, als);
>
> I don't think we should expose the ACPI pathname of the device here.
> If we really need something in sysfs, I think some kind of link to the
> underlying device would be better.
What I mean to say here is that if we need a connection to the ACPI
pathname (and we might, especially for debugging), I think the
connection should be between "ACPI0008:00" and the pathname, not between
something in /sys/class/als/... and the pathname.
Then you could have a link under /sys/class/als/... to the ACPI0008:00
stuff.
Bjorn
next prev parent reply other threads:[~2009-08-06 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 8:31 [RFC PATCH V2 2/2] introduce ACPI ALS device driver Zhang Rui
2009-08-06 15:09 ` Bjorn Helgaas
2009-08-06 16:50 ` Bjorn Helgaas [this message]
2009-08-06 18:52 ` Greg KH
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=1249577458.457.40.camel@dc7800.home \
--to=bjorn.helgaas@hp.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=rui.zhang@intel.com \
/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