From: Andri Yngvason <andri.yngvason@marel.com>
To: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: RFC: Improve and consolidate error state change
Date: Tue, 16 Sep 2014 14:36:16 +0000 [thread overview]
Message-ID: <54184AE0.6050100@marel.com> (raw)
In-Reply-To: <5411F360.4020103@marel.com>
On fim 11.sep 2014 19:09, Andri Yngvason wrote:
> Hello,
>
> As we've discussed in a recent thread, error state changes are
> inconsistent
> between platforms. Wolfgang had already done some work on this a
> couple of
> years ago, but it never made it into the kernel.
> See: http://thread.gmane.org/gmane.linux.can/201
...
>
> I've also edited the mscan, flexcan and sja1000 drivers to use this
> function,
> but I actually don't have hardware to test this on any other platforms.
>
> Is anyone willing to test this on other platforms?
>
> I'll post patches, when there's been feedback on this.
>
Ping?
next prev parent reply other threads:[~2014-09-16 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 19:09 RFC: Improve and consolidate error state change Andri Yngvason
2014-09-16 14:36 ` Andri Yngvason [this message]
2014-09-16 14:50 ` 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=54184AE0.6050100@marel.com \
--to=andri.yngvason@marel.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).