From: "Max S." <max@schneidersoft.net>
To: linux-can <linux-can@vger.kernel.org>
Subject: struct can_bittiming/struct can_berr_counter
Date: Sat, 12 Jan 2013 20:29:34 +0000 [thread overview]
Message-ID: <1358022574.2504.23.camel@blackbox> (raw)
In-Reply-To: <50EB20C0.4000201@hartkopp.net>
Hello,
What is the reason why struct can_bittiming and struct can_berr_counter
use __u32 for all its members?
In the case of txerr and rxerr are those not even limited to 255 in the
CAN specification?
Max S.
next prev parent reply other threads:[~2013-01-12 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-29 22:50 max is back Max S.
2013-01-07 19:23 ` Oliver Hartkopp
2013-01-12 20:29 ` Max S. [this message]
2013-01-15 16:40 ` struct can_bittiming/struct can_berr_counter Wolfgang Grandegger
2013-01-15 16:46 ` Wolfgang Grandegger
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=1358022574.2504.23.camel@blackbox \
--to=max@schneidersoft.net \
--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).