From: Sam Ravnborg <sam@ravnborg.org>
To: torvalds@transmeta.com, davej@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] kernel-doc: Fix warnings [4/9]
Date: Wed, 24 Jul 2002 23:33:36 +0200 [thread overview]
Message-ID: <20020724233336.C12782@mars.ravnborg.org> (raw)
In-Reply-To: <20020724232021.A12622@mars.ravnborg.org>; from sam@ravnborg.org on Wed, Jul 24, 2002 at 11:20:21PM +0200
# 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.434 -> 1.435
# scripts/kernel-doc 1.10 -> 1.11
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/07/24 sam@mars.ravnborg.org 1.435
# [PATCH] kernel-doc: Fix warnings [4/9]
# During processing of skbuff.h three warnings were issued,
# becasue members of an enum within a struct were nor documented.
# This patch fixes kernel-doc not to spit out these non-valid warnings.
# Originally by Thunder.
# --------------------------------------------
#
diff -Nru a/scripts/kernel-doc b/scripts/kernel-doc
--- a/scripts/kernel-doc Wed Jul 24 23:26:04 2002
+++ b/scripts/kernel-doc Wed Jul 24 23:26:04 2002
@@ -646,6 +646,7 @@
print " <programlisting>\n";
print $args{'type'}." ".$args{'struct'}." {\n";
foreach $parameter (@{$args{'parameterlist'}}) {
+ defined($args{'parameterdescs'}{$parameter}) || next;
($args{'parameterdescs'}{$parameter} ne $undescribed) || next;
$type = $args{'parametertypes'}{$parameter};
if ($type =~ m/([^\(]*\(\*)\s*\)\s*\(([^\)]*)\)/) {
@@ -666,6 +667,7 @@
print " <variablelist>\n";
foreach $parameter (@{$args{'parameterlist'}}) {
+ defined($args{'parameterdescs'}{$parameter}) || next;
($args{'parameterdescs'}{$parameter} ne $undescribed) || next;
print " <varlistentry>";
print " <term>$parameter</term>\n";
next prev parent reply other threads:[~2002-07-24 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 21:20 [PATCH] Made 'make sgmldocs' work again after serial merge [1/9] Sam Ravnborg
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 ` Sam Ravnborg [this message]
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=20020724233336.C12782@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®