From: Paul Jackson <pj@sgi.com>
To: miaox@cn.fujitsu.com
Cc: 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 21:22:11 -0500 [thread overview]
Message-ID: <20080529212211.0e794c81.pj@sgi.com> (raw)
In-Reply-To: <483F6367.1040701@cn.fujitsu.com>
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.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-05-30 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 7:07 [RFC] [PATCH 1/2] cpusets: restructure the function update_cpumask() and update_nodemask() 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 [this message]
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
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=20080529212211.0e794c81.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.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