On 2017-01-02 22:13, Jonathan Cameron wrote:
>
>
> On 2 January 2017 20:47:58 GMT+00:00, Peter Rosin wrote:
>> On 2017-01-02 19:05, Jonathan Cameron wrote:
>>> On 02/01/17 16:01, Peter Rosin wrote:
On 2017-01-01 12:00, Jonathan Cameron wrote:
> On 30/11/16 08:17, Peter Rosin wrote:
Am 02.01.2017 um 10:33 schrieb Jani Nikula :
> On Mon, 02 Jan 2017, Markus Heiser wrote:
>> IMO we should no longer investigate in the kernel_doc perl script, which
>> is at it ends. Instead we should merge the python version from my linuxdoc
>> project (BTW: with, we get man-pages from and lint
On 01/02/2017 07:22 PM, Hui Chun Ong wrote:
On Thu, 2016-12-29 at 02:09 -0800, Guenter Roeck wrote:
On 12/28/2016 10:56 PM, Hui Chun Ong wrote:
Add support for the watchdog timer on PXI Embedded Controller.
Reviewed-by: Guenter Roeck
Signed-off-by: Hui Chun Ong
---
v5: Add Reviewed-by.
The
On Thu, 2016-12-29 at 02:09 -0800, Guenter Roeck wrote:
> On 12/28/2016 10:56 PM, Hui Chun Ong wrote:
> >
> > Add support for the watchdog timer on PXI Embedded Controller.
> >
> > Reviewed-by: Guenter Roeck
> > Signed-off-by: Hui Chun Ong
> > ---
> > v5: Add Reviewed-by.
> There is no need to
"Luis R. Rodriguez" writes:
>> Maybe a similar hack for try_then_request_module(), but many places seem
>> to open-code request_module() so it's not as trivial...
Hi Luis, Jessica (who is the main module maintainer now),
Back from break, sorry about delay.
> Right, out of ~350 request_m
On Monday, January 02, 2017 03:39:20 PM Jonathan Corbet wrote:
> On Mon, 02 Jan 2017 23:05:31 +0100
> "Rafael J. Wysocki" wrote:
>
> > > From: Rafael J. Wysocki
> > >
> > > The references to drivers/base/power/main.c and
> > > drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst
On Mon, 02 Jan 2017 23:05:31 +0100
"Rafael J. Wysocki" wrote:
> > From: Rafael J. Wysocki
> >
> > The references to drivers/base/power/main.c and
> > drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst
> > are confusing. They both cause descriptions of functions that are
> > n
On Monday, December 19, 2016 09:36:39 PM Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The references to drivers/base/power/main.c and
> drivers/acpi/scan.c from Documentation/driver-api/infrastructure.rst
> are confusing. They both cause descriptions of functions that are
> not relevan
On 2 January 2017 20:47:58 GMT+00:00, Peter Rosin wrote:
>On 2017-01-02 19:05, Jonathan Cameron wrote:
>> On 02/01/17 16:01, Peter Rosin wrote:
>>> On 2017-01-01 12:00, Jonathan Cameron wrote:
On 30/11/16 08:17, Peter Rosin wrote:
> Analog Devices ADG792A/G is a triple 4:1 mux.
>
>>
On 2017-01-02 19:05, Jonathan Cameron wrote:
> On 02/01/17 16:01, Peter Rosin wrote:
>> On 2017-01-01 12:00, Jonathan Cameron wrote:
>>> On 30/11/16 08:17, Peter Rosin wrote:
Analog Devices ADG792A/G is a triple 4:1 mux.
Signed-off-by: Peter Rosin
>>> Few comments inline. Worth add
On Wed, Dec 28, 2016 at 09:51:37PM +, Colin Ian King wrote:
> From: Colin Ian King
>
> Signed-off-by: Colin Ian King
Acked-by: Guenter Roeck
> ---
> Documentation/hwmon/ds1621| 8
> Documentation/thermal/nouveau_thermal | 2 +-
> 2 files changed, 5 insertions(+), 5 d
On 01/02/2017 12:16 PM, Arnaldo Carvalho de Melo wrote:
> Em Thu, Dec 29, 2016 at 11:13:39AM -0500, Waiman Long escreveu:
>> This microbenchmark simulates how the use of different futex types
>> can affect the actual performanace of userspace mutex locks. The
>> usage is:
>>
>> perf bench f
On 02/01/17 11:00, Peter Rosin wrote:
> On 2017-01-01 12:24, Jonathan Cameron wrote:
>> On 30/11/16 08:17, Peter Rosin wrote:
>>> Analog Devices ADG792A/G is a triple 4:1 mux.
>>>
>>> Signed-off-by: Peter Rosin
>> Looks pretty good. Some minor suggestions inline.
>>
>> This convinced me of two thi
On 02/01/17 16:01, Peter Rosin wrote:
> On 2017-01-01 12:00, Jonathan Cameron wrote:
>> On 30/11/16 08:17, Peter Rosin wrote:
>>> Analog Devices ADG792A/G is a triple 4:1 mux.
>>>
>>> Signed-off-by: Peter Rosin
>> Few comments inline. Worth adding anything about the gpio (output pins) to
>> the b
Em Thu, Dec 29, 2016 at 11:13:39AM -0500, Waiman Long escreveu:
> This microbenchmark simulates how the use of different futex types
> can affect the actual performanace of userspace mutex locks. The
> usage is:
>
> perf bench futex mutex
Showing the tool output is preferred, trim it if
On 2017-01-01 12:00, Jonathan Cameron wrote:
> On 30/11/16 08:17, Peter Rosin wrote:
>> Analog Devices ADG792A/G is a triple 4:1 mux.
>>
>> Signed-off-by: Peter Rosin
> Few comments inline. Worth adding anything about the gpio (output pins) to
> the binding at this stage as well? Would certainly
On 2017-01-01 16:38, Andy Shevchenko wrote:
> On Wed, Nov 30, 2016 at 10:17 AM, Peter Rosin wrote:
>> This is a generic simple i2c mux that uses the generic multiplexer
>> subsystem to do the muxing.
>
>> +static const struct of_device_id i2c_mux_of_match[] = {
>> + { .compatible = "i2c-mux
Note that, in order to produce the correct Docbook markup, the "." or "->"
must be separated from the member name in the regex's captured fields. For
consistency, this change is applied to $type_member and $type_member_func
too, not just to $type_member_xml.
List mode only prints the struct name,
An inline function can have an attribute, as in include/linux/log2.h,
and kernel-doc handles this already for simple cases. However,
some attributes have arguments (e.g. the "target" attribute).
Handle those too.
Furthermore, attributes could be at the beginning of a function
declaration, before
$type_struct_full and friends are only used by the restructuredText
backend, because it needs to separate enum/struct/typedef/union from
the name of the type. However, $type_struct is *also* used by the rST
backend. This is confusing.
This patch replaces $type_struct's use in the rST backend wit
A prototype like
/**
* foo - sample definition
* @bar: a parameter
*/
int foo(int (*bar)(int x,
int y));
is currently producing
.. c:function:: int foo (int (*bar) (int x,int y)
sample definition
**Parameters**
The restructuredText output includes both the parameter type and
the name for functions and function-typed members. Do the same
for docbook.
Signed-off-by: Paolo Bonzini
---
scripts/kernel-doc | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/kernel-doc b/scripts
Hi,
these patches are the result of my experiments with using kernel-doc
for QEMU's documentation. Patches 1 and 2 should be relatively
straightforward, as they are simple bugfixes. Patches 3 to 5, instead,
are making the docbook backend (and the others too) more consistent with
the input and ou
On Mon, 2017-01-02 at 08:28 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> It's maintained by Seth Forshe for a long time now.
>
Both applied, thanks.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majord...@vger.kernel.org
Mo
On 2017-01-01 12:24, Jonathan Cameron wrote:
> On 30/11/16 08:17, Peter Rosin wrote:
>> Analog Devices ADG792A/G is a triple 4:1 mux.
>>
>> Signed-off-by: Peter Rosin
> Looks pretty good. Some minor suggestions inline.
>
> This convinced me of two things:
> 1. Need a separate subsystem directory
On Mon, 02 Jan 2017, Markus Heiser wrote:
> IMO we should no longer investigate in the kernel_doc perl script, which
> is at it ends. Instead we should merge the python version from my linuxdoc
> project (BTW: with, we get man-pages from and lint of kernel-doc comments).
>
> To see how this python
On 2 January 2017 09:26:03 GMT+00:00, Jani Nikula
wrote:
>On Sun, 01 Jan 2017, Jonathan Cameron wrote:
>> Hi All,
>>
>> I have very little idea how the internals of the kernel-doc
>processing
>> code work, but was wondering if it would be possible to suppress
>warnings
>> of the type:
>>
>> .
On Sun, 01 Jan 2017, Jonathan Cameron wrote:
> Hi All,
>
> I have very little idea how the internals of the kernel-doc processing
> code work, but was wondering if it would be possible to suppress warnings
> of the type:
>
> ./include/linux/iio/buffer.h:142: warning: Excess struct/union/enum/type
On 2 January 2017 09:14:34 GMT+00:00, Peter Rosin wrote:
>On 2016-12-31 17:19, Jonathan Cameron wrote:
>> On 30/11/16 08:16, Peter Rosin wrote:
>>> Add a new minimalistic subsystem that handles multiplexer
>controllers.
>>> When multiplexers are used in various places in the kernel, and the
>>>
On 2016-12-31 17:19, Jonathan Cameron wrote:
> On 30/11/16 08:16, Peter Rosin wrote:
>> Add a new minimalistic subsystem that handles multiplexer controllers.
>> When multiplexers are used in various places in the kernel, and the
>> same multiplexer controller can be used for several independent th
Am 01.01.2017 um 15:05 schrieb Jonathan Cameron :
> Hi All,
>
> I have very little idea how the internals of the kernel-doc processing
> code work, but was wondering if it would be possible to suppress warnings
> of the type:
>
> ./include/linux/iio/buffer.h:142: warning: Excess struct/union/en
31 matches
Mail list logo
