From: Sam Ravnborg <sam@ravnborg.org>
To: torvalds@transmeta.com, davej@suse.de, rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Made 'make sgmldocs' work again after serial merge [1/9]
Date: Wed, 24 Jul 2002 23:20:21 +0200 [thread overview]
Message-ID: <20020724232021.A12622@mars.ravnborg.org> (raw)
9 patches follows dealing with the kernel-documentation.
1 Changes after move of serial drivers
2-4 Corrections to kernel-doc, mainly forward porting from 2.4
5-7 Rewrite of docproc, docbook makefile + related stuff
8-9 Changes in top-level makefile
Except for the changes in kernel-doc this is equal to the single patch
submitted yesterday. But reading the patch I felt a few more comments were
needed, so I decided to split it up a bit.
Applies to Linus'es BK-latest.
Sam
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.431 -> 1.432
# Documentation/DocBook/kernel-api.tmpl 1.15 -> 1.16
# Documentation/DocBook/Makefile 1.27 -> 1.28
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/07/24 sam@mars.ravnborg.org 1.432
# [PATCH] Made 'make sgmldocs' work again after serial merge [1/8]
# o Changed targets in documentation/DocBook/Makefile
# o New filenames in DocBook/kernel-api.tmpl
# --------------------------------------------
#
diff -Nru a/Documentation/DocBook/Makefile b/Documentation/DocBook/Makefile
--- a/Documentation/DocBook/Makefile Wed Jul 24 22:06:00 2002
+++ b/Documentation/DocBook/Makefile Wed Jul 24 22:06:00 2002
@@ -107,7 +107,8 @@
$(TOPDIR)/kernel/printk.c \
$(TOPDIR)/drivers/net/net_init.c \
$(TOPDIR)/drivers/net/8390.c \
- $(TOPDIR)/drivers/char/serial.c \
+ $(TOPDIR)/drivers/serial/core.c \
+ $(TOPDIR)/drivers/serial/8250.c \
$(TOPDIR)/drivers/pci/pci.c \
$(TOPDIR)/drivers/hotplug/pci_hotplug_core.c \
$(TOPDIR)/drivers/hotplug/pci_hotplug_util.c \
diff -Nru a/Documentation/DocBook/kernel-api.tmpl b/Documentation/DocBook/kernel-api.tmpl
--- a/Documentation/DocBook/kernel-api.tmpl Wed Jul 24 22:06:00 2002
+++ b/Documentation/DocBook/kernel-api.tmpl Wed Jul 24 22:06:00 2002
@@ -305,7 +305,8 @@
<chapter id="uart16x50">
<title>16x50 UART Driver</title>
-!Edrivers/char/serial.c
+!Edrivers/serial/core.c
+!Edrivers/serial/8250.c
</chapter>
<chapter id="z85230">
next reply other threads:[~2002-07-24 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 21:20 Sam Ravnborg [this message]
2002-07-24 21:31 ` [PATCH] kernel-doc: Improved support for man-page generation [2/9] Sam Ravnborg
2002-07-24 21:32 ` [PATCH] kernel-doc: Generate valid DocBook syntax [3/9] Sam Ravnborg
2002-07-24 21:33 ` [PATCH] kernel-doc: Fix warnings [4/9] Sam Ravnborg
2002-07-24 21:34 ` [PATCH] docbook: scripts/docproc improved [5/9] Sam Ravnborg
2002-07-24 21:36 ` [PATCH] docbook: Makefile cleanup [6/9] Sam Ravnborg
2002-07-24 21:37 ` [PATCH] docbook: Update documentation to reflect new docproc [7/9] Sam Ravnborg
2002-07-24 21:38 ` [PATCH] docbook: Move script target in top-level file [8/9] Sam Ravnborg
2002-07-24 21:39 ` [PATCH] docbook: Call docbook makefile with -f [9/9] Sam Ravnborg
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=20020724232021.A12622@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.com \
/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).