From: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
To: kime-Z4QKGCRq86k@public.gmane.org
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CAN State Information
Date: Thu, 08 Dec 2011 20:15:00 +0100 [thread overview]
Message-ID: <4EE10CB4.2090604@grandegger.com> (raw)
In-Reply-To: <166589D0B9DD2547A1319599B9BADA1FC1981F-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
Hello James,
On 12/08/2011 09:43 AM, kime-Z4QKGCRq86k@public.gmane.org wrote:
> Hello,
> Thanks for the response. I am using can_get_state() as part of my start_CAN routine. After, I call can_do_start(), I read the state to see if I need to do bus-off recovery. So it is not a frequent call. I was able to see the states correctly on all four CAN channels with "ip -d -s link".
OK, just to be sure. Does the "canconfig canX state" from the
Pengutronix canutils list the state correctly for any device?
I just tried here and it works fine.
> I updated the code in plx_pci.c to include support for the IXXAT card. I wanted to ask you how to submit the changes since I have not done it before. I attached a patch file.
Nice! A patch should be submitted as *inline* mail to the linux-can
*and* netdev mailing list with a proper subject, patch description and
signed-off-by line. The subject line should be something like:
"[PATCH net-next] can: plx_pci: add support for IXXAT PCI cards"
It's best to use git to create and send the patch but for simple patches
it doesn't really matter.
Wolfgang.
next prev parent reply other threads:[~2011-12-08 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166589D0B9DD2547A1319599B9BADA1FC1960C@vsv-exchange.ixxat.intranet.priv>
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1960C-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-06 15:26 ` CAN State Information Wolfgang Grandegger
[not found] ` <4EDE342E.8030102-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-06 18:54 ` Wolfram Sang
2011-12-08 8:43 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1981F-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-08 19:15 ` Wolfgang Grandegger [this message]
2011-12-09 8:03 ` kime
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC19968-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 8:15 ` Wolfgang Grandegger
[not found] ` <4EE1C3BF.70104-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:19 ` Wolfgang Grandegger
[not found] ` <4EE1C47A.7080507-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:45 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1998A-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 9:00 ` Wolfgang Grandegger
2011-12-09 13:41 ` kime
2011-12-09 14:49 ` Wolfgang Grandegger
[not found] ` <4EE2200E.4060403-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-12 10:21 ` kime-Z4QKGCRq86k
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=4EE10CB4.2090604@grandegger.com \
--to=wg-5yr1bzd7o62+xt7jha+gda@public.gmane.org \
--cc=kime-Z4QKGCRq86k@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.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).