From: John Whitmore <arigead@gmail.com>
To: linux-can@vger.kernel.org
Subject: Documentation/networking/can.txt
Date: Mon, 2 Dec 2013 22:49:17 +0000 [thread overview]
Message-ID: <20131202224916.GA5577@griso.site> (raw)
Been lurking on this list for a while trying to get a feel for it. First post,
poking my head above the wall, so to speak.
I'll start with the Documentation in the Linux kernel. At the moment, on a
netbook, running from the Linus' git tree so perhaps I'm on the wrong git tree
for communicating with this mailing list, but given the number of different
git trees, I can't keep my head straight. Let me know if I'd be better on a
different git tree.
I've been reading (and re-reading) a few of the networking docs and specifically
can.txt as I'm starting to do some work on Linux CAN. To date I've been
working on MCP2515's connected to small micro-controllers creating my own
networks. I'm now hoping to plug a RaspberryPi into my CAN Networks.
There are a few typos in can.txt that aren't a big deal, but I could try send
a patch file for them. My bigger question is with regard to section 3.3 which
mentions Kconfig options "CAN_RAW_USER" and "CAN_BCM_USER". I've searched in
the linux "make menuconfig" for these options and neither exist. grep'd the
code, and didn't find an occurrence, outside can.txt, so I assume these two
options could be removed from the text?
Finally, for the moment, section 7 references:
http://developer.berlios.de/projects/socketcan
this link is no longer correct as it points to another URL, so perhaps this
reference could be updated?
I can attempt a patch but let me know against which git tree? Maybe that info
could go into can.txt as well.
jwhitmore
next reply other threads:[~2013-12-02 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 22:49 John Whitmore [this message]
2013-12-03 6:56 ` Documentation/networking/can.txt Oliver Hartkopp
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=20131202224916.GA5577@griso.site \
--to=arigead@gmail.com \
--cc=linux-can@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).