On Sat, Jan 09, 2021 at 02:45:06PM -0800, Saravana Kannan wrote: > The device link device's name was of the form: > <supplier-dev-name>--<consumer-dev-name> > > 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: > <supplier-bus-name>:<supplier-dev-name>--<consumer-bus-name>:<consumer-dev-name> > > [1] - https://lore.kernel.org/lkml/20201229033440.32142-1-michael@xxxxxxxx/ > > Cc: stable@xxxxxxxxxxxxxxx > Fixes: 287905e68dd2 ("driver core: Expose device link details in sysfs") > Reported-by: Michael Walle <michael@xxxxxxxx> > Signed-off-by: Saravana Kannan <saravanak@xxxxxxxxxx> > --- > 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
