From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: [PATCH V3] leds: trigger: Introduce an USB port trigger Date: Wed, 24 Aug 2016 17:04:57 -0400 Message-ID: <20160824210457.GC4305@kroah.com> References: <20160823220404.9887-1-zajec5@gmail.com> <20160824092225.GB23180@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Richard Purdie , Jacek Anaszewski , Felipe Balbi , Peter Chen , "linux-usb@vger.kernel.org" , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Jonathan Corbet , Ezequiel Garcia , Matthias Brugger , Boris Brezillon , Geert Uytterhoeven , Stephan Linz , "open list:DOCUMENTATION" , open list , "open list:LED SUBSYSTEM" List-Id: linux-leds@vger.kernel.org On Wed, Aug 24, 2016 at 11:29:51AM +0200, Rafał Miłecki wrote: > On 24 August 2016 at 11:22, Greg KH wrote: > > On Wed, Aug 24, 2016 at 12:03:29AM +0200, Rafał Miłecki wrote: > >> +static ssize_t ports_show(struct device *dev, struct device_attribute *attr, > >> + char *buf) > >> +{ > >> + struct led_classdev *led_cdev = dev_get_drvdata(dev); > >> + struct usbport_trig_data *usbport_data = led_cdev->trigger_data; > >> + struct usbport_trig_port *port; > >> + ssize_t ret = 0; > >> + int len; > >> + > >> + list_for_each_entry(port, &usbport_data->ports, list) { > >> + len = sprintf(buf + ret, "%s\n", port->name); > >> + if (len >= 0) > >> + ret += len; > >> + } > >> + > >> + return ret; > >> +} > > > > sysfs is "one value per file", here you are listing a bunch of things in > > one sysfs file. Please don't do that. > > OK. What do you think about creating "ports" subdirectory and creating > file-per-port in it? Then I'd need to bring back something like > "new_port" and "remove_port". Does it sound OK? Maybe, I don't know. Why is "USB" somehow unique here? Why isn't this the same for PCI slots/ports? pccard? sdcard? thunderbolt? thanks, greg k-h