From: Daniel Drake <dan@reactivated.net>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] (2.6.0-test6-bk) DocBook: Kernel-api build fix
Date: Sat, 04 Oct 2003 17:53:40 +0100 [thread overview]
Message-ID: <3F7EFB14.7050909@reactivated.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
In the latest -bk tree for 2.6.0-test6, net/netsyms.c has been removed.
The kernel-api DocBook docs still refer to this file, and because this file is gone, "make htmldocs" and similar fails.
Here's a patch to remove the reference and fix this docbook problem.
Daniel.
[-- Attachment #2: docbook-kernel-api-fix.patch --]
[-- Type: text/plain, Size: 372 bytes --]
--- linux-2.6.0-test6/Documentation/DocBook/kernel-api.tmpl 2003-09-28 11:34:13.000000000 +0100
+++ linux/Documentation/DocBook/kernel-api.tmpl 2003-10-04 17:43:27.345686600 +0100
@@ -318,6 +318,5 @@
<!-- Needs ksyms to list additional exported symbols, but no specific doc.
docproc do not care about sgml commants.
!Dkernel/ksyms.c
-!Dnet/netsyms.c
-->
</book>
reply other threads:[~2003-10-04 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F7EFB14.7050909@reactivated.net \
--to=dan@reactivated.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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