From: "Halil Demirezen" <nitrium@bilmuh.ege.edu.tr>
To: "Rusty Lynch" <rusty@linux.co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Coding style question] XXX_register or register_XXX
Date: Thu, 21 Nov 2002 03:02:06 +0800 [thread overview]
Message-ID: <20021121030206.M48633@bilmuh.ege.edu.tr> (raw)
In-Reply-To: <001701c290ef$8417f020$94d40a0a@amr.corp.intel.com>
> Is there an accepted standard on naming for registration functions?
> If have a foo object that other things can register and unregister
> with, should the function names be:
> int foo_register(&something);
> int foo_unregister(&something);
really, that would make the entire kernel code a little
simplier to understand.
On the same way, we can say why there is not an accepted standard on
naming lock functions, such as
spinlock, rwlock and so on..
That would be more efficient to understand the code...
However, where is flexibility?
-hd
next prev parent reply other threads:[~2002-11-21 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 23:49 Rusty Lynch
2002-11-20 19:02 ` Halil Demirezen [this message]
2002-11-21 1:08 ` Robert Love
2002-11-21 1:14 ` Arnaldo Carvalho de Melo
2002-11-21 3:53 Perez-Gonzalez, Inaky
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=20021121030206.M48633@bilmuh.ege.edu.tr \
--to=nitrium@bilmuh.ege.edu.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linux.co.intel.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
all inboxes | Powered by JetHome®