netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <oliver@hartkopp.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: [CAN] Update documentation of struct sockaddr_can (for 2.6.25)
Date: Sun, 13 Apr 2008 14:26:29 +0200	[thread overview]
Message-ID: <4801FBF5.2050209@hartkopp.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

Hello Dave,

as there are still some things pending for the final 2.6.25 please add 
the following patch to fix the current documentation.

Thanks,
Oliver

------------------

The struct sockaddr_can has been simplified in the code review process. 
This patch updates this simplification also in the associated 
documentation in can.txt .

Signed-off-by: Oliver Hartkopp <oliver@hartkopp.net>





[-- Attachment #2: can.txt.diff --]
[-- Type: text/x-diff, Size: 837 bytes --]

diff --git a/Documentation/networking/can.txt b/Documentation/networking/can.txt
index f1b2de1..641d2af 100644
--- a/Documentation/networking/can.txt
+++ b/Documentation/networking/can.txt
@@ -281,10 +281,10 @@ solution for a couple of reasons:
             sa_family_t can_family;
             int         can_ifindex;
             union {
-                    struct { canid_t rx_id, tx_id; } tp16;
-                    struct { canid_t rx_id, tx_id; } tp20;
-                    struct { canid_t rx_id, tx_id; } mcnet;
-                    struct { canid_t rx_id, tx_id; } isotp;
+                    /* transport protocol class address info (e.g. ISOTP) */
+                    struct { canid_t rx_id, tx_id; } tp;
+
+                    /* reserved for future CAN protocols address information */
             } can_addr;
     };
 

             reply	other threads:[~2008-04-13 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 12:26 Oliver Hartkopp [this message]
2008-04-15  7:46 ` [CAN] Update documentation of struct sockaddr_can (for 2.6.25) David Miller

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=4801FBF5.2050209@hartkopp.net \
    --to=oliver@hartkopp.net \
    --cc=davem@davemloft.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).