All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Paul Jackson <pj@sgi.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: Fri, 30 May 2008 10:16:07 +0800	[thread overview]
Message-ID: <483F6367.1040701@cn.fujitsu.com> (raw)
In-Reply-To: <20080529205344.4ba1efdb.pj@sgi.com>

on 2008-5-30 9:53 Paul Jackson wrote:
> Miao wrote:
>> I think that it is unnecessary to change cpuset_cpus_allowed_locked()'s comment
>> because it isn't a static function, it is a extern function
> 
> Yes, you are correct.  My mistake.  Sorry.
> 

I check kernel/cpuset.c and find many static functions with "/**" comment.
So I want to remove the special commenting convention for them.


  reply	other threads:[~2008-05-30  2:16 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 [this message]
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
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=483F6367.1040701@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.