From: Jason Ferguson <jferg3@swbell.net>
To: linux-kernel@vger.kernel.org
Cc: marcelo@conectiva.com.br
Subject: [PATCH] Fix make pdfdocs
Date: Sat, 09 Feb 2002 08:29:15 -0600 [thread overview]
Message-ID: <1013264955.512.4.camel@werewolf> (raw)
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
Hi, Im actually resubmitting a patch I dug up in the archives from David
Gomez back in October to fix a problem when creating the
deviceiobook.pdf file.
Details and patch below.
Jason
i, this patch fix an error when generating postscript files. Error is
caused by the absence of documentation in include/asm/io.h.
--- deviceiobookold.tmpl Sun Oct 28 22:28:36 2001
+++ deviceiobook.tmpl Sun Oct 28 22:28:45 2001
@@ -224,9 +224,5 @@
</chapter>
- <chapter id="pubfunctions">
- <title>Public Functions Provided</title>
- !Einclude/asm-i386/io.h
- </chapter>
</book>
David Gómez
"The question of whether computers can think is just like the question
of
whether submarines can swim." -- Edsger W. Dijkstra
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
reply other threads:[~2002-02-09 14:27 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=1013264955.512.4.camel@werewolf \
--to=jferg3@swbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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