mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>,
	"linux-doc@vger.kernel.org List" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST backends
Date: Mon, 23 Jan 2017 14:58:29 +0100	[thread overview]
Message-ID: <6fae4fd5-2fa9-c1e6-1177-c85d9aadcd17@redhat.com> (raw)
In-Reply-To: <CFFA583C-EEF3-40D2-80F9-E66E39BE1372@darmarit.de>



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

  reply	other threads:[~2017-01-23 13:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 15:22 Paolo Bonzini
2017-01-02 15:22 ` [PATCH 1/5] kernel-doc: cleanup parameter type in function-typed arguments Paolo Bonzini
2017-01-02 15:22 ` [PATCH 2/5] kernel-doc: strip attributes even if they have an argument Paolo Bonzini
2017-01-02 15:22 ` [PATCH 3/5] kernel-doc: include parameter type in docbook output Paolo Bonzini
2017-01-02 15:22 ` [PATCH 4/5] kernel-doc: make member highlighting available in all backends Paolo Bonzini
2017-01-02 15:22 ` [PATCH 5/5] kernel-doc: make highlights more homogenous for the various backends Paolo Bonzini
2017-01-03  9:57 ` [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST backends Jani Nikula
2017-01-04 15:13   ` Paolo Bonzini
2017-01-04 15:40     ` Jani Nikula
2017-01-04 22:06 ` Jonathan Corbet
2017-01-23 13:42   ` Markus Heiser
2017-01-23 13:58     ` Paolo Bonzini [this message]
2017-01-23 14:38       ` Markus Heiser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6fae4fd5-2fa9-c1e6-1177-c85d9aadcd17@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®