From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751444AbdLIVcy (ORCPT ); Sat, 9 Dec 2017 16:32:54 -0500 Received: from mail.kernel.org ([198.145.29.99]:54404 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751229AbdLIVcv (ORCPT ); Sat, 9 Dec 2017 16:32:51 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A94E62191B Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=luto@kernel.org X-Google-Smtp-Source: AGs4zMZs74ToWuKpos93gSoHNxX5c4rts0LCil11P9BsnJIkldYWNfR0RJF5vSL7YFWuwxIG8XLVp4aIuvnmQJuG2Ik= MIME-Version: 1.0 In-Reply-To: <1512790860266.96149@Dell.com> References: <1512786861-1014-1-git-send-email-mario.limonciello@dell.com> <1512786861-1014-2-git-send-email-mario.limonciello@dell.com> <1512790860266.96149@Dell.com> From: Andy Lutomirski Date: Sat, 9 Dec 2017 13:32:29 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 1/2] platform/x86: wmi: prefix sysfs files in /sys/bus/wmi with the ACPI device To: Mario Limonciello Cc: Darren Hart , Andy Shevchenko , "linux-kernel@vger.kernel.org" , Platform Driver , Andrew Lutomirski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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-bus directory? > > Yep, but the symlink created in /sys/bus/wmi/devices isn't. > That's where the kernel complains about duplicate sysfs > attributes. > > It's not exactly a pretty path I submitted, but it does avoid > those collisions. > > Example (with this in place from /sys/bus/wmi/devices): > lrwxrwxrwx 1 root root 0 Dec 8 21:39 PNP0C14:04-70FE8229-D03B-4214-A1C6-1F884B1A892A -> ../../../devices/platform/PNP0C14:04/wmi_bus/wmi_bus-PNP0C14:04/PNP0C14:04-70FE8229-D03B-4214-A1C6-1F884B1A892A Right, I saw that in the cover letter right after sending this. Greg, is there a cleaner way to deal with this? There are two instances of the same bus type, each of which would like to have a device called "70FE8229-D03B-4214-A1C6-1F884B1A892A". Can we somehow rename the symlinks without renaming the device, or are we just supposed to prefix the device name like Mario is doing here?