From: Andrew Morton <akpm@osdl.org>
To: johnpol@2ka.mipt.ru
Cc: linux-kernel@vger.kernel.org
Subject: Re: connector.h
Date: Thu, 31 Mar 2005 23:44:21 -0800 [thread overview]
Message-ID: <20050331234421.0bf0f8ea.akpm@osdl.org> (raw)
In-Reply-To: <1112339394.9334.70.camel@uganda>
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>
> 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?
I think it's better to document these things in the code. Those structs
which are communicated to userspace should be described in connector.txt
because they are part of the API. But a lot of the structs you have there
are purely knerel-internal.
> > > struct cn_msg
> > > {
> >
> > Please do
> >
> > struct cn_msg {
>
> Neither structure declaration should have opening brace on the new
> string?
I don't understand your question.
We lay out struct definitions thusly:
struct foo {
int a;
int b;
};
prev parent reply other threads:[~2005-04-01 7:45 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 ` connector.h Evgeniy Polyakov
2005-04-01 7:44 ` Andrew Morton [this message]
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=20050331234421.0bf0f8ea.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=johnpol@2ka.mipt.ru \
--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
all inboxes | Powered by JetHome®