linux-kernel - Re: [PATCH 2/3] cpusets: restructure the function update_cpumask() and update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20080530105658.1b2f4839.pj@sgi.com>
Date:	Fri, 30 May 2008 10:56:58 -0500
From:	Paul Jackson <pj@....com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	miaox@...fujitsu.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, menage@...gle.com
Subject: Re: [PATCH 2/3] cpusets: restructure the function update_cpumask()
 and update_nodemask()

Alan wrote:
> Trivial only: The kernel-doc bits should be /**, 3 of them.

It took me a minute to parse this comment (pre-coffee morning fog ;).

I take it that you're noticing, Alan, that the header comments for
the functions update_tasks_cpumask() and update_tasks_nodemask(), and
perhaps one other function, are already in kernel-doc format, except
for one detail -- they currently open with '/*' instead of '/**',
and you're recommending the trivial change '/*' ==> '/**' for these
cases.

Yes - Miao commented these new functions in kernel-doc format, all but
the '/**', by my request, which now stands NAQ'd.

So, yes, '/**' should be used on any kernel/cpuset.c function comment
that is otherwise already in kernel-doc format.

Again, thank-you.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/