From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 8/8] MAINTAINERS: update documentation entries
Date: Wed, 10 Nov 2010 11:53:50 -0800 [thread overview]
Message-ID: <1289418830734@xenotime.net> (raw)
In-Reply-To: <1289418830794@xenotime.net>
From: Randy Dunlap <randy.dunlap@oracle.com>
Add explicit filename supported (scripts/kernel-doc) and add my
documentation quilt tree location to the MAINTAINERS file.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
--- linux-2.6.37-rc1-git8.orig/MAINTAINERS
+++ linux-2.6.37-rc1-git8/MAINTAINERS
@@ -2008,6 +2008,7 @@ F: drivers/hwmon/dme1737.c
DOCBOOK FOR DOCUMENTATION
M: Randy Dunlap <rdunlap@xenotime.net>
S: Maintained
+F: scripts/kernel-doc
DOCKING STATION DRIVER
M: Shaohua Li <shaohua.li@intel.com>
@@ -2018,6 +2019,7 @@ F: drivers/acpi/dock.c
DOCUMENTATION
M: Randy Dunlap <rdunlap@xenotime.net>
L: linux-doc@vger.kernel.org
+T: quilt oss.oracle.com/~rdunlap/kernel-doc-patches/current/
S: Maintained
F: Documentation/
--
next prev parent reply other threads:[~2010-11-10 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 19:53 [for review: PATCH 1/8] kernel-doc: escape xml for structs Randy Dunlap
2010-11-10 19:53 ` [PATCH 7/8] Documentation: remove anticipatory scheduler info Randy Dunlap
2010-11-11 11:10 ` Jens Axboe
2010-11-10 19:53 ` [PATCH 5/8] Documentation/development-process: use -next trees instead of staging Randy Dunlap
2010-11-10 19:53 ` [PATCH 4/8] Documentation: change email address for Hans Koch Randy Dunlap
2010-11-10 19:53 ` [PATCH 2/8] Documentation: make configfs example code simpler, clearer Randy Dunlap
2010-11-10 19:53 ` [PATCH 6/8] Documentation/development-process: more staging info Randy Dunlap
2010-11-10 19:53 ` Randy Dunlap [this message]
2010-11-10 19:53 ` [PATCH 3/8] Documentation/gpio.txt: explain poll/select usage 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=1289418830734@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.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