On Sat, Dec 09, 2017 at 01:32:29PM -0800, Andy Lutomirski wrote:
> On Fri, Dec 8, 2017 at 7:41 PM, wrote:
> >>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> >>> wrote:
> >>>
> >>> It's possible for the same GUID to show up on as system twice.
> >>> This means using solely the GUID for identi
On Sat, Dec 09, 2017 at 01:32:29PM -0800, Andy Lutomirski wrote:
> On Fri, Dec 8, 2017 at 7:41 PM, wrote:
> >>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> >>> wrote:
> >>>
> >>> It's possible for the same GUID to show up on as system twice.
> >>> This means using solely the GUID for identi
On Fri, Dec 8, 2017 at 7:41 PM, wrote:
>>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
>>> wrote:
>>>
>>> It's possible for the same GUID to show up on as system twice.
>>> This means using solely the GUID for identify the file will not
>>> be sufficient.
>>
>>Isn't the file already in a per-
>> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
>> wrote:
>>
>> It's possible for the same GUID to show up on as system twice.
>> This means using solely the GUID for identify the file will not
>> be sufficient.
>
>Isn't the file already in a per-bus directory?
Yep, but the symlink created in /
--Andy
> On Dec 8, 2017, at 6:34 PM, Mario Limonciello
> wrote:
>
> It's possible for the same GUID to show up on as system twice.
> This means using solely the GUID for identify the file will not
> be sufficient.
Isn't the file already in a per-bus directory?
It's possible for the same GUID to show up on as system twice.
This means using solely the GUID for identify the file will not
be sufficient.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/wmi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/platform/x86
6 matches
Mail list logo