From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: [PATCH 0/6] 9pfs: convert Doxygen -> kerneldoc format
Date: Thu, 3 Mar 2022 14:40:56 +0100 [thread overview]
Message-ID: <cover.1646314856.git.qemu_oss@crudebyte.com> (raw)
This patch set converts occurrences of API doc comments from Doxygen format
into kerneldoc format. No behaviour change whatsoever.
Christian Schoenebeck (6):
9pfs/9p.h: convert Doxygen -> kerneldoc format
9pfs/codir.c: convert Doxygen -> kerneldoc format
9pfs/9p.c: convert Doxygen -> kerneldoc format
9pfs/9p-util.h: convert Doxygen -> kerneldoc format
9pfs/coth.h: drop Doxygen format on v9fs_co_run_in_worker()
fsdev/p9array.h: convert Doxygen -> kerneldoc format
fsdev/p9array.h | 38 ++++++++++++++++-------------
hw/9pfs/9p-util.h | 10 ++++----
hw/9pfs/9p.c | 62 ++++++++++++++++++++++++++---------------------
hw/9pfs/9p.h | 12 ++++-----
hw/9pfs/codir.c | 30 +++++++++++------------
hw/9pfs/coth.h | 4 +--
6 files changed, 84 insertions(+), 72 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-03 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:40 Christian Schoenebeck [this message]
2022-03-03 12:28 ` [PATCH 1/6] 9pfs/9p.h: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-03 12:52 ` [PATCH 2/6] 9pfs/codir.c: " Christian Schoenebeck
2022-03-03 13:12 ` [PATCH 3/6] 9pfs/9p.c: " Christian Schoenebeck
2022-03-03 13:20 ` [PATCH 4/6] 9pfs/9p-util.h: " Christian Schoenebeck
2022-03-03 13:22 ` [PATCH 5/6] 9pfs/coth.h: drop Doxygen format on v9fs_co_run_in_worker() Christian Schoenebeck
2022-03-03 13:37 ` [PATCH 6/6] fsdev/p9array.h: convert Doxygen -> kerneldoc format Christian Schoenebeck
2022-03-04 7:39 ` [PATCH 0/6] 9pfs: " Greg Kurz
2022-03-04 10:37 ` Christian Schoenebeck
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=cover.1646314856.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).