[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6fae4fd5-2fa9-c1e6-1177-c85d9aadcd17@redhat.com>
Date: Mon, 23 Jan 2017 14:58:29 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Markus Heiser <markus.heiser@...marit.de>
Cc: Jonathan Corbet <corbet@....net>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org List" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST
backends
On 23/01/2017 14:42, Markus Heiser wrote:
>
> Am 04.01.2017 um 23:06 schrieb Jonathan Corbet <corbet@....net>:
>
>> On Mon, 2 Jan 2017 16:22:22 +0100
>> Paolo Bonzini <pbonzini@...hat.com> wrote:
>>
>>> 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 output of the rST backend.
>>>
>>> I am not sure what is the state of the kernel-doc non-rST backends;
>>> but there are still several books using the docbook workflow, so I'm
>>> trying my luck and sending the patches anyway. :)
>>
>> I've played with them a bit, and they don't seem to break things, so I'll
>> go ahead and apply them.
>
> Hi Paolo !
>
> Sorry for my late reply, I'am testing patch 2:
>
> https://www.mail-archive.com/linux-doc@vger.kernel.org/msg08503.html
>
> but I can't find any changes in the reST output (even not in include/linux/log2.h
> you mentioned). May I'm a bit blind today, so can you give me an example where
> the patch takes effect?
I found this with QEMU. You need to test with an inline function which
has attributes with arguments.
Paolo
Powered by blists - more mailing lists