From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: connector.h
Date: Fri, 01 Apr 2005 11:09:54 +0400 [thread overview]
Message-ID: <1112339394.9334.70.camel@uganda> (raw)
In-Reply-To: <20050331173101.769f5c67.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
On Thu, 2005-03-31 at 17:31 -0800, Andrew Morton wrote:
> >
> > struct cb_id
> > {
> > __u32 idx;
> > __u32 val;
> > };
>
> It is vital that all data structures be skilfully commented - they are the
> key to understanding the code. Why the struct exists, which actor passes
> it to which other actor(s), whether the data structure is communicated with
> userspace, what other data structures it is aggregated with or linked to,
> locking rules, etc.
It is described in Documentation/connector/connector.txt.
Should it also be placed here?
> > struct cn_msg
> > {
>
> Please do
>
> struct cn_msg {
Neither structure declaration should have opening brace on the new
string?
> >
> > #define CN_CBQ_NAMELEN 32
>
> Commentary?
Maximum allowed callback name - name will be truncated if
it exceeds that limit.
I will place this doc in the code.
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-01 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 1:31 connector.h Andrew Morton
2005-04-01 7:09 ` Evgeniy Polyakov [this message]
2005-04-01 7:44 ` connector.h Andrew Morton
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=1112339394.9334.70.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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