linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: rusty@rustcorp.com.au, zaitcev@yahoo.com
Subject: Re: [PATCH] Update Documentation/DocBook/kernel-locking.tmpl
Date: Thu, 11 Dec 2003 20:00:55 -0800	[thread overview]
Message-ID: <20031211200055.778ca906.rddunlap@osdl.org> (raw)
In-Reply-To: <20031211153349.18368656.rddunlap@osdl.org>

| 
| This has needed doing for a while.  Reviews welcome. 
| 
| As an attachment because it's about 64k "raw".


Some could be fuser errors (with docbook stylesheets etc.)...


a.  uses "gloss-timer" and "gloss-timers": choose one

b.  docbook complained about many unclosed or unmatched instances
    of </sect1>, </chapter>, </listitem>, etc.

c.  docbook complains about some 'C' syntactic items that are
inside <LiteralLayout> or <programlisting>.  E.g.:

- 'cache' in
	list_for_each_entry(i, &cache, list)

- 'obj-' in
	list_del(&obj->list);

- 'cache_lock' in
	down(&cache_lock);

(see the pattern: '&' shouldn't be special inside these blocks,
or at least that's how I think about it, but the software disagrees)


- docbook (at least my version) dislikes these #includes:
 #include <linux/list.h>
 #include <linux/slab.h>
 #include <linux/string.h>
+#include <linux/rcupdate.h>
 #include <asm/semaphore.h>
 #include <asm/errno.h>


I'd read it for content soonish.

Thanks for the update.

--
~Randy

       reply	other threads:[~2003-12-12  4:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031211153349.18368656.rddunlap@osdl.org>
2003-12-12  4:00 ` Randy.Dunlap [this message]
2003-12-12  6:04   ` [PATCH] Update Documentation/DocBook/kernel-locking.tmpl Rusty Russell
2003-12-11  8:57 Rusty Russell

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=20031211200055.778ca906.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zaitcev@yahoo.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).