From: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: [PATCH] include/linux/mutex.h: unclear reference to convention
Date: Tue, 25 Sep 2007 01:11:05 -0700 (PDT) [thread overview]
Message-ID: <713129.73007.qm@web52009.mail.re2.yahoo.com> (raw)
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.
__________________________________
Alles was der Gesundheit und Entspannung dient. BE A BETTER MEDIZINMANN! www.yahoo.de/clever
next reply other threads:[~2007-09-25 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 8:11 Matti Linnanvuori [this message]
2007-09-25 15:33 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 7:38 Matti Linnanvuori
2007-09-24 14:49 ` Randy Dunlap
2007-09-22 8:41 Matti Linnanvuori
2007-09-22 17:35 ` Randy Dunlap
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=713129.73007.qm@web52009.mail.re2.yahoo.com \
--to=mattilinnanvuori@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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