lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 23 Jan 2017 14:58:29 +0100
From:   Paolo Bonzini <>
To:     Markus Heiser <>
Cc:     Jonathan Corbet <>,
        " List" <>,
        " List" <>
Subject: Re: [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST

On 23/01/2017 14:42, Markus Heiser wrote:
> Am 04.01.2017 um 23:06 schrieb Jonathan Corbet <>:
>> On Mon,  2 Jan 2017 16:22:22 +0100
>> Paolo Bonzini <> 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:
> 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.


Powered by blists - more mailing lists