Acked-by: Mario Limonciello <mario.limoncie...@dell.com>

> -----Original Message-----
> From: Mika Westerberg [mailto:mika.westerb...@linux.intel.com]
> Sent: Monday, October 23, 2017 4:52 AM
> To: Andy Shevchenko <andriy.shevche...@linux.intel.com>
> Cc: Jonathan Corbet <cor...@lwn.net>; linux-doc@vger.kernel.org; Andreas
> Noever <andreas.noe...@gmail.com>; Limonciello, Mario
> <mario_limoncie...@dell.com>
> Subject: Re: [PATCH v1 1/2] thunderbolt: Make pathname to force_power shorter
> 
> On Fri, Oct 20, 2017 at 09:49:37PM +0300, Andy Shevchenko wrote:
> > WMI is the bus inside kernel, so, we may access the GUID via
> > /sys/bus/wmi instead of doing this through /sys/devices path.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevche...@linux.intel.com>
> 
> Looks reasonable. Adding Mario who added this if he has any objections.
> 
> Acked-by: Mika Westerberg <mika.westerb...@linux.intel.com>
> 
> > ---
> >  Documentation/admin-guide/thunderbolt.rst | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/admin-guide/thunderbolt.rst
> b/Documentation/admin-guide/thunderbolt.rst
> > index de50a8561774..9b55952039a6 100644
> > --- a/Documentation/admin-guide/thunderbolt.rst
> > +++ b/Documentation/admin-guide/thunderbolt.rst
> > @@ -230,7 +230,7 @@ If supported by your machine this will be exposed by the
> WMI bus with
> >  a sysfs attribute called "force_power".
> >
> >  For example the intel-wmi-thunderbolt driver exposes this attribute in:
> > -  /sys/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-
> PNP0C14:00/86CCFD48-205E-4A77-9C48-2021CBEDE341/force_power
> > +  /sys/bus/wmi/devices/86CCFD48-205E-4A77-9C48-
> 2021CBEDE341/force_power
> >
> >    To force the power to on, write 1 to this attribute file.
> >    To disable force power, write 0 to this attribute file.
> > --
> > 2.14.2
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to