From: Evgeniy Polyakov <zbr@ioremap.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [W1] Updated documentation.
Date: Fri, 5 Dec 2008 09:28:54 +0300 [thread overview]
Message-ID: <20081205062854.GA24227@ioremap.net> (raw)
In-Reply-To: <49386D75.2030302@oracle.com>
Hi Randy.
On Thu, Dec 04, 2008 at 03:53:25PM -0800, Randy Dunlap (randy.dunlap@oracle.com) wrote:
> > --- a/Documentation/w1/w1.netlink
> > +++ b/Documentation/w1/w1.netlink
> > @@ -17,25 +17,27 @@ Protocol.
> > [struct cn_msg] - connector header. It's length field is equal to size of the attached data.
>
> (not in this patch, but:) Its
Yup :)
> > -Each connector message can include one or more w1_netlink_msg with zero of more attached w1_netlink_cmd messages.
> > +Each connector message can include one or more w1_netlink_msg with zero or more attached w1_netlink_cmd messages.
>
> Please limit lines to a maximum of 80 characters. Around 72 would be Good.
> (here and elsewhere)
Will change.
> > For event messages there are no w1_netlink_cmd embedded structures, only connector header
> > and w1_netlink_msg strucutre with "len" field being zero and filled type (one of event types)
>
> structure
> > + cn_msg (CN_W1_IDX.CN_W1_VAL as id, len is equal to sizeof(struct
> > + w1_netlink_msg) plus number of masters multipled by 4)
>
> multiplied
Changed.
> > @@ -82,10 +98,10 @@ Connector [1] specific documentation.
> > Each connector message includes two u32 fields as "address".
> > w1 uses CN_W1_IDX and CN_W1_VAL defined in include/linux/connector.h header.
>
> uses them for what?
They define destination address in connector subsystem.
> > Each message also includes sequence and acknowledge numbers.
> > -Sequence number for event messages is appropriate bus master sequence number increased with
> > +Sequence number for event messages is appropriate bus master sequence number increased with
>
> Line ends with space. Please check for that throughout the file.
Ok.
> > @@ -93,6 +109,6 @@ Additional documantion, source code examples.
>
> documentation
Changed
> I'll plan to review the entire doc file.
Great, thank you!
I will roll out updated version today with this changes and fixed patch
mentioned by Frederik.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-12-05 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 14:50 [W1] extend userspace commands Evgeniy Polyakov
2008-12-04 14:50 ` Evgeniy Polyakov
2008-12-04 14:50 ` [W1] Added list masters w1 command Evgeniy Polyakov
2008-12-04 14:50 ` [W1] Added touch block command Evgeniy Polyakov
2008-12-04 14:50 ` [W1] Updated documentation Evgeniy Polyakov
2008-12-04 14:50 ` [W1] List slaves commands Evgeniy Polyakov
2008-12-04 14:50 ` [W1] W1 search/alarm search documentation Evgeniy Polyakov
2008-12-04 23:53 ` [W1] Updated documentation Randy Dunlap
2008-12-05 6:28 ` Evgeniy Polyakov [this message]
2008-12-04 15:42 ` [W1] Added touch block command Frederik Deweerdt
2008-12-04 15:58 ` Evgeniy Polyakov
2008-12-04 15:41 ` [W1] Added list masters w1 command Frederik Deweerdt
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=20081205062854.GA24227@ioremap.net \
--to=zbr@ioremap.net \
--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