Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp1511450pxb; Sun, 10 Jan 2021 00:35:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJy1D5N7xv+MyrEc4Nd28mXVe2IdFd56OrCQctIZtM2fcym3rQBGTO7CBTcXwdSN4ykRfHqT X-Received: by 2002:aa7:c58a:: with SMTP id g10mr10504599edq.315.1610267756983; Sun, 10 Jan 2021 00:35:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610267756; cv=none; d=google.com; s=arc-20160816; b=KiB1JKw8xmr8tavFBEsmh/GrnV1v+/YEOt5FOMdAwnNTDD5TLzk/3ngZEchwzvX8GL VAJeoBiDCUsrl5Z7qtubJCoFBc/oSY7MKjC4gn1hHgr/0qQJqUmks0o4IjJtk6DLkuoM TWQ5hpo0LVOCfgK1mwomSC3JGwuyGwvKMYqoqyyJqXyQdJt0QkgvjiSgLrzZOtlaeXLs N3kocjroVchOjf1sRbmb74H/qHZ+eRWLDTVDQaGEiAQ0YuatlQWjeAp3cvdgbPoLORar 0Rdh1EH2+t7krWMH+quSbONrSLqj7SRyxnww830ngPo+Tdnv0qTdGk+4AKvpqzWN0yGu wi+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=Aj9TypjzDFt6M8A71q73h1/7zGex0NUMuT4baUUmjY0=; b=XJpbd332dDe/ERw3GyJ2s4FGgRKdpqUZiWU8jOxNhc+zYb8nx1kwesEjI+aDDRq8yK Huzxl/pVNRmdy2P4XeZJSG/iLdN8m+o+mSEQRRZq3xlQffJuJpyDHYoJzIlEMZa8rUnw NFFhOUlIwHxPajtV7Q4uLjUnoV5BXjIs+cCypXWFs0+BSEQDh+57ql8re2s4piPvmPMP SZ15K2Ba0FtV412GE6VSpy865soqTD5XVR7O2q2zmbVc5kbxAuugMl8QPS1IXv9dIfcx GaRpJABAbgQFlrt1tOO6QsqYwLhyj4MyHezDmCzgZ9Xw11DYa2bPtVrP6TSCSzXzdQr3 R61g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="Po/iyCts"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u7si5745838edb.213.2021.01.10.00.35.14; Sun, 10 Jan 2021 00:35:56 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b="Po/iyCts"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726562AbhAJIdP (ORCPT + 99 others); Sun, 10 Jan 2021 03:33:15 -0500 Received: from mail.kernel.org ([198.145.29.99]:59012 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726142AbhAJIdP (ORCPT ); Sun, 10 Jan 2021 03:33:15 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 9672D22273; Sun, 10 Jan 2021 08:32:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1610267554; bh=jBOMBbrY8ejC7e+1+GDTy1/aQY2hSrvpdZYSjkPw/QM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Po/iyCtsXWMi0rag0UBrCjRhfDTpm6aVF+VtIidWI8HaZp02lfbr8xW6H7zgpvCH0 pwy5FVyUMJ4KMuO4gOPMlsy1KRg6a2PQXok50o3yFrdeevGhuG+knKriybE7FytU1f hZm2VN/nPaBHOkCRgs85ouLdG96G4jCbibDaz+Jk= Date: Sun, 10 Jan 2021 09:32:30 +0100 From: Greg Kroah-Hartman To: Saravana Kannan Cc: "Rafael J. Wysocki" , stable@vger.kernel.org, Michael Walle , kernel-team@android.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4] driver core: Fix device link device name collision Message-ID: References: <20210109224506.1254201-1-saravanak@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210109224506.1254201-1-saravanak@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jan 09, 2021 at 02:45:06PM -0800, Saravana Kannan wrote: > The device link device's name was of the form: > -- > > This can cause name collision as reported here [1] as device names are > not globally unique. Since device names have to be unique within the > bus/class, add the bus/class name as a prefix to the device names used to > construct the device link device name. > > So the devuce link device's name will be of the form: > :--: > > [1] - https://lore.kernel.org/lkml/20201229033440.32142-1-michael@walle.cc/ > > Cc: stable@vger.kernel.org > Fixes: 287905e68dd2 ("driver core: Expose device link details in sysfs") > Reported-by: Michael Walle > Signed-off-by: Saravana Kannan > --- > Documentation/ABI/testing/sysfs-class-devlink | 4 +-- > .../ABI/testing/sysfs-devices-consumer | 5 ++-- > .../ABI/testing/sysfs-devices-supplier | 5 ++-- > drivers/base/core.c | 27 ++++++++++--------- > include/linux/device.h | 12 +++++++++ > 5 files changed, 35 insertions(+), 18 deletions(-) > Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - This looks like a new version of a previously submitted patch, but you did not list below the --- line any changes from the previous version. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what needs to be done here to properly describe this. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot