From: Randy Dunlap <rdunlap@xenotime.net>
To: Paul Jackson <pj@sgi.com>
Cc: miaox@cn.fujitsu.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, menage@google.com
Subject: Re: [RFC] [PATCH 1/2] cpusets: restructure the function update_cpumask() and update_nodemask()
Date: Fri, 30 May 2008 08:32:51 -0700 [thread overview]
Message-ID: <20080530083251.8f06e092.rdunlap@xenotime.net> (raw)
In-Reply-To: <20080530012537.87454a8d.pj@sgi.com>
On Fri, 30 May 2008 01:25:37 -0500 Paul Jackson wrote:
> Randy wrote:
> > Does that help? your understanding of kernel-doc or your decision?
>
> Well, I get the difference between E (exported) and I (non-exported)
> now. And I see that one could prepare documents using SGML templates
> that contained one, or the other of these, for any kernel source files
> of interest.
>
> I'm stuck on the next step of this decision.
>
> Usually, when I am preparing documens, I know what document I am
> preparing and have an idea who is in its audience.
>
> I have never seen or heard of a document using the "/**" kernel-doc
> entries of kernel/cpuset.c, and I have no idea who actually has (in
> the past or present, not just hypothetically) read such or why.
You are certainly welcome to add kernel/cpuset.c to kernel-api.tmpl or any other
appropriate docbook file. I have been known to do things like that as well. :)
> So I'm kinda shootin in the dark here.
>
> So, mostly just to be consistent with my previous call, because I enjoy
> being a stubborn retard, I continue to prefer that file static routines
> in kernel/cpuset.c not have "/**" kernel-doc markers on their comments,
> and I would still welcome a patch from Miao removing the ones already
> there.
>
> Enough of this discussion, from me at least.
---
~Randy
"He closes his eyes and drops the goggles. You can't get hurt
by looking at a bitmap. Or can you?"
next prev parent reply other threads:[~2008-05-30 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 7:07 Miao Xie
2008-05-29 8:16 ` Paul Jackson
2008-05-30 1:51 ` Miao Xie
2008-05-30 1:53 ` Paul Jackson
2008-05-30 2:16 ` Miao Xie
2008-05-30 2:22 ` Paul Jackson
2008-05-30 3:30 ` Randy Dunlap
2008-05-30 3:57 ` Paul Jackson
2008-05-30 4:27 ` Randy Dunlap
2008-05-30 5:24 ` Paul Jackson
2008-05-30 6:25 ` Paul Jackson
2008-05-30 9:46 ` Alan Cox
2008-05-30 15:22 ` Paul Jackson
2008-05-30 15:32 ` Randy Dunlap [this message]
2008-05-30 15:39 ` Randy Dunlap
2008-05-30 16:07 ` Paul Jackson
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=20080530083251.8f06e092.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--cc=pj@sgi.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®