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: Thu, 29 May 2008 20:30:42 -0700 [thread overview]
Message-ID: <20080529203042.19f76f09.rdunlap@xenotime.net> (raw)
In-Reply-To: <20080529212211.0e794c81.pj@sgi.com>
On Thu, 29 May 2008 21:22:11 -0500 Paul Jackson wrote:
> Miao wrote:
> > I check kernel/cpuset.c and find many static functions with "/**" comment.
> > So I want to remove the special commenting convention for them.
>
> Right you are. Offhand, in kernel/cpuset.c, I see:
>
> static int cpuset_test_cpumask(struct task_struct *tsk,
> static void cpuset_change_cpumask(struct task_struct *tsk,
> static int update_cpumask(struct cpuset *cs, char *buf)
> static void cpuset_do_move_task(struct task_struct *tsk,
> static void move_member_tasks_to_cpuset(struct cpuset *from, struct cpuset *to)
>
> all having "/**" header comments. I would be glad to Ack a patch
> from you to fix such comments. Thank-you.
Uh.. We strongly want non-static functions to be documented via kernel-doc.
For static functions, it's up to the maintainer/developer whether to do that
or not. But if the functions already have kernel-doc, there's no strong
reason to remove it. And these look good currently, so I see no
good reason to change them.
---
~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 3:17 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 [this message]
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
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=20080529203042.19f76f09.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®