From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] doc: Add section for C API documentation
Date: Wed, 17 Apr 2024 11:19:14 +0200 [thread overview]
Message-ID: <20240417091914.GB708026@pevik> (raw)
In-Reply-To: <Zh502b2hn9K8S4PQ@yuki>
Hi,
> Hi!
> > +The C API documentation is written using
> Maybe to be a bit more clear:
> "The C API documentation is generated from headers using" ?
+1
with that change:
Reviewed-by: Petr Vorel <pvorel@suse.cz>
If you both agree, I'll merge it with this change.
Kind regards,
Petr
> > +`kernel-doc <https://return42.github.io/linuxdoc/linuxdoc-howto/kernel-doc-syntax.html>`_
> > +syntax which is supported by Sphinx via
> > +`linuxdoc <https://pypi.org/project/linuxdoc/>`_ extension.
> > --
> > 2.35.3
> > --
> > Mailing list info: https://lists.linux.it/listinfo/ltp
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-04-17 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 9:18 [LTP] [PATCH v1] doc: Add section for C API documentation Andrea Cervesato
2024-04-16 12:53 ` Cyril Hrubis
2024-04-17 9:19 ` Petr Vorel [this message]
2024-04-17 9:20 ` Andrea Cervesato via ltp
2024-04-17 10:07 ` Petr Vorel
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=20240417091914.GB708026@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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