[PATCH 1/3] documentation/scsi: Remove nodisconnect parameter

2016-08-26 Thread Finn Thain
The driver that used the 'nodisconnect' parameter was removed in commit 565bae6a4a8f ("[SCSI] 53c7xx: kill driver"). Related documentation was cleaned up in commit f37a7238d379 ("[SCSI] 53c7xx: fix removal fallout"), except for the remaining two mentions that are removed here. Signed-off-by: Finn

Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

2016-08-26 Thread Baoquan He
On 08/26/16 at 08:45am, "Zhou, Wenjian/周文剑" wrote: > Hi Baoquan, > > Sorry, I misunderstood it before. > Thanks for your detailed explanation. > > Hi Jon and Baoquan, I'm confused about how to adjust the kdump.txt. > Does the patch set v9 still OK? Yeah, I think it's OK. Let's wait for Jon's fee

Re: [PATCH v9 1/2] Documentation: kdump: remind user of nr_cpus

2016-08-26 Thread Baoquan He
On 08/25/16 at 01:10pm, Jonathan Corbet wrote: > On Wed, 24 Aug 2016 13:06:45 +0800 > Baoquan He wrote: > > > Hi Jon, do you think change as below is OK to you? > > So nr_cpus is the maximum value, and maxcpus is the current number. > Figures. No wonder the documentation is confusing... Yes. T

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-26 Thread Pavel Machek
On Thu 2016-08-25 20:48:04, Jacek Anaszewski wrote: > On 08/25/2016 04:30 PM, Alan Stern wrote: > >On Thu, 25 Aug 2016, Jacek Anaszewski wrote: > > > >>I'd see it as follows: > >> > >>#cat available_ports > >>#1-1 1-2 2-1 > >> > >>#echo "1-1" > new_port > >> > >>#cat observed_ports > >>#1-1 > >> >

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-26 Thread Pavel Machek
On Thu 2016-08-25 11:04:38, Jacek Anaszewski wrote: > On 08/25/2016 10:29 AM, Rafał Miłecki wrote: > >On 25 August 2016 at 10:03, Jacek Anaszewski > >wrote: > >>On 08/24/2016 07:52 PM, Rafał Miłecki wrote: > >>> > >>>From: Rafał Miłecki > >>> > >>>This commit adds a new trigger responsible for t

Re: [PATCH] docs: make kernel-doc handle varargs properly

2016-08-26 Thread kbuild test robot
to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Jonathan-Corbet/docs-make-kernel-doc-handle-varargs-properly/20160826-213158 reproduce: make htmldocs

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-26 Thread Rafał Miłecki
On 25 August 2016 at 20:48, Jacek Anaszewski wrote: > On 08/25/2016 04:30 PM, Alan Stern wrote: >> >> On Thu, 25 Aug 2016, Jacek Anaszewski wrote: >> >>> I'd see it as follows: >>> >>> #cat available_ports >>> #1-1 1-2 2-1 >>> >>> #echo "1-1" > new_port >>> >>> #cat observed_ports >>> #1-1 >>> >>>

Re: [PATCH V4] leds: trigger: Introduce an USB port trigger

2016-08-26 Thread Rafał Miłecki
On 25 August 2016 at 14:49, Greg KH wrote: > On Thu, Aug 25, 2016 at 10:03:52AM +0200, Rafał Miłecki wrote: >> +static void usbport_trig_activate(struct led_classdev *led_cdev) >> +{ >> + struct usbport_trig_data *usbport_data; >> + int err; >> + >> + usbport_data = kzalloc(sizeof(*usb

[PATCH V2] Documentation: move oneshot trigger attributes documentation to ABI

2016-08-26 Thread Rafał Miłecki
From: Rafał Miłecki Documentation of sysfs interface should be in ABI in the first place. This moves relevant part of documentation and mentions where to look for it. Fix trivial typos whilst we are at it. Signed-off-by: Rafał Miłecki --- V2: s/Default/Defaults/ s/ / / s/change/changes

Re: [PATCH] Documentation: move oneshot trigger attributes documentation to ABI

2016-08-26 Thread Jacek Anaszewski
Hi Rafał, Thanks for the patch. We could possibly correct one linguistic issue whilst we are at it. Please take a look below. On 08/25/2016 11:38 AM, Rafał Miłecki wrote: From: Rafał Miłecki Documentation of sysfs interface should be in ABI in the first place. This moves relevant part of docu

[PATCH] docs: make kernel-doc handle varargs properly

2016-08-26 Thread Jonathan Corbet
As far as I can tell, the handling of "..." arguments has never worked right, so any documentation provided was ignored in favor of "variable arguments." This makes kernel-doc handle "@...:" as documented. It does *not* fix spots in kerneldoc comments that don't follow that convention, but they a

Re: [PATCH 0/3] RFC: The beginning of a proper driver-api book

2016-08-26 Thread Jani Nikula
On Fri, 26 Aug 2016, Mauro Carvalho Chehab wrote: > Em Fri, 26 Aug 2016 11:34:38 +0200 > Markus Heiser escreveu: > >> Am 23.08.2016 um 16:43 schrieb Mauro Carvalho Chehab >> : >> >> > Em Mon, 22 Aug 2016 14:57:40 -0600 >> > Jonathan Corbet escreveu: >> > >> >> This short series convers devi

Re: [PATCH 0/3] RFC: The beginning of a proper driver-api book

2016-08-26 Thread Mauro Carvalho Chehab
Em Fri, 26 Aug 2016 11:34:38 +0200 Markus Heiser escreveu: > Am 23.08.2016 um 16:43 schrieb Mauro Carvalho Chehab > : > > > Em Mon, 22 Aug 2016 14:57:40 -0600 > > Jonathan Corbet escreveu: > > > >> This short series convers device-drivers.tmpl into the RST format, splits > >> it up, and set

Re: [PATCH 0/3] RFC: The beginning of a proper driver-api book

2016-08-26 Thread Markus Heiser
Am 23.08.2016 um 16:43 schrieb Mauro Carvalho Chehab : > Em Mon, 22 Aug 2016 14:57:40 -0600 > Jonathan Corbet escreveu: > >> This short series convers device-drivers.tmpl into the RST format, splits >> it up, and sets up the result under Documentation/driver-api/. For added >> fun, I've taken