All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: miaox@cn.fujitsu.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	Paul Jackson <pj@sgi.com>, Paul Menage <menage@google.com>
Subject: Re: [PATCH 2/3] cpusets: restructure the function update_cpumask() and update_nodemask()
Date: Fri, 30 May 2008 10:53:02 +0100	[thread overview]
Message-ID: <20080530105302.0f447003@core> (raw)
In-Reply-To: <483FAE13.5080101@cn.fujitsu.com>

> --- a/kernel/cpuset.c
> +++ b/kernel/cpuset.c
> @@ -766,6 +766,38 @@ static void cpuset_change_cpumask(struct task_struct *tsk,
>  }
>  
>  /*

Trivial only: The kernel-doc bits should be /**, 3 of them. The fourth
function doesn't have kernel-doc headers/format so is fine as is (or
could grow them - hint ;))

Alan


  reply	other threads:[~2008-05-30 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30  7:34 [PATCH 2/3] cpusets: restructure the function update_cpumask() and update_nodemask() Miao Xie
2008-05-30  9:53 ` Alan Cox [this message]
2008-05-30 15:56   ` 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=20080530105302.0f447003@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --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 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.