linux-kernel - Re: [PATCH] include/linux/mutex.h: unclear reference to convention

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: <20070925083348.b8860569.randy.dunlap@oracle.com>
Date:	Tue, 25 Sep 2007 08:33:48 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Matti Linnanvuori <mattilinnanvuori@...oo.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] include/linux/mutex.h: unclear reference to convention

On Tue, 25 Sep 2007 01:11:05 -0700 (PDT) Matti Linnanvuori wrote:

> If you want to maintain the convention of documenting the interface only in .c files, 
> you should write the convention in so many places in .h files that no one could overlook it.
> But I think the convention is bad and it would be better to document the interface also in
> .h files where it is defined. The convention is bad because it requires people to jump to
> other files to understand .h files.

Then we would have comments in multiple places and they would
undoubtedly get out of sync.  When that happens, which one do
you use?  Bad.

I'll find some place to document this convention anyway.  Maybe
it will help.

---
~Randy
Phaedrus says that Quality is about caring.
-
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/