From: Andrew Morton <akpm@linux-foundation.org>
To: Alex Shi <alex.shi@intel.com>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
rusty@rustcorp.com.au, paul.gortmaker@windriver.com,
kosaki.motohiro@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask: add a few comments of cpumask functions
Date: Fri, 13 Jul 2012 15:37:56 -0700 [thread overview]
Message-ID: <20120713153756.78234398.akpm@linux-foundation.org> (raw)
In-Reply-To: <4FC38A77.8090700@intel.com>
On Mon, 28 May 2012 22:23:51 +0800
Alex Shi <alex.shi@intel.com> wrote:
> Current few cpumask functions' purposes are not quite clear. Stupid
> user like myself need to dig into details for clear function
> purpose and return value.
> Add few explanation for them is helpful.
>
It appears that Rusty has applied at least some of this patch to
linux-next. Without reading it ;)
> --- a/include/linux/cpumask.h
> +++ b/include/linux/cpumask.h
> @@ -271,6 +271,7 @@ static inline void cpumask_clear_cpu(int cpu, struct cpumask *dstp)
> * cpumask_test_cpu - test for a cpu in a cpumask
> * @cpu: cpu number (< nr_cpu_ids)
> * @cpumask: the cpumask pointer
> + * Returns 1 if the 'cpu' is in the old bitmap of 'cpumask', otherwise returns 0
In kerneldoc we refer to function arguments by prefixing them with a
'@', not by surrounding them with single quotes. So this should be
* Returns 1 if @cpu is in the old bitmap of @cpumask, otherwise returns 0
And the same applies to the other comments. So can you please grab the
latest linux-next, prepare a fixup patch and also check that the patch
is complete - not all of your changes have been applied.
next prev parent reply other threads:[~2012-07-13 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 9:02 Alex Shi
2012-05-28 12:47 ` Srivatsa S. Bhat
2012-05-28 13:49 ` Alex Shi
2012-05-28 14:23 ` Alex Shi
2012-07-13 22:37 ` Andrew Morton [this message]
2012-07-16 2:34 ` Alex Shi
2012-07-16 7:35 ` Rusty Russell
2012-07-16 8:01 ` Alex Shi
2012-05-28 15:25 ` Srivatsa S. Bhat
2012-05-29 1:16 ` Alex Shi
2012-05-30 10:40 ` Alex Shi
2012-05-30 10:49 ` KOSAKI Motohiro
2012-05-31 8:15 ` Alex Shi
2012-06-04 1:37 ` Rusty Russell
2012-06-04 1:36 ` Rusty Russell
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=20120713153756.78234398.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rusty@rustcorp.com.au \
--cc=srivatsa.bhat@linux.vnet.ibm.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
Powered by JetHome