From: Randy Dunlap <rd.dunlab@gmail.com>
To: linux1394-devel@lists.sourceforge.net
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 0/5] FireWire: clean up kernel-doc, add Documentation chapter
Date: Fri, 13 Apr 2018 18:27:17 -0700 [thread overview]
Message-ID: <20180414012722.17420-1-rd.dunlab@gmail.com> (raw)
This patch series cleans up kernel-doc warnings in several
FireWire source files and then adds a Documentation driver-api
chapter for FireWire.
[PATCH v3 1/5] FireWire: clean up firewire-cdev.h kernel-doc
[PATCH v3 2/5] FireWire: clean up core-iso.c kernel-doc
[PATCH v3 3/5] FireWire: clean up core-transaction.c kernel-doc
[PATCH v3 4/5] FireWire: add a Documentation driver-api chapter
[PATCH v3 5/5] FireWire: add driver-api Introduction section
Documentation/driver-api/firewire.rst | 50 +++++++++++++++++++++++-
Documentation/driver-api/index.rst | 1
drivers/firewire/core-iso.c | 7 +++
drivers/firewire/core-transaction.c | 10 ++++
include/uapi/linux/firewire-cdev.h | 22 ++++++----
5 files changed, 81 insertions(+), 9 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-14 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 1:27 Randy Dunlap [this message]
2018-04-14 1:27 ` [PATCH v3 1/5] FireWire: clean up firewire-cdev.h kernel-doc Randy Dunlap
2018-04-14 1:27 ` [PATCH v3 2/5] FireWire: clean up core-iso.c kernel-doc Randy Dunlap
2018-04-14 1:27 ` [PATCH v3 3/5] FireWire: clean up core-transaction.c kernel-doc Randy Dunlap
2018-04-14 1:27 ` [PATCH v3 4/5] FireWire: add a Documentation driver-api chapter Randy Dunlap
2018-04-14 1:27 ` [PATCH v3 5/5] FireWire: add driver-api Introduction section Randy Dunlap
2018-04-16 2:10 ` [PATCH v2 0/5] FireWire: clean up kernel-doc, add Documentation chapter Takashi Sakamoto
2018-06-16 23:55 ` Randy Dunlap
2018-08-19 3:48 ` Randy Dunlap
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=20180414012722.17420-1-rd.dunlab@gmail.com \
--to=rd.dunlab@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
--cc=rdunlap@infradead.org \
--cc=stefanr@s5r6.in-berlin.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;
as well as URLs for NNTP newsgroup(s).