From: Marc Kleine-Budde <mkl@pengutronix.de>
To: T Thayer <tthayer.linux@gmail.com>
Cc: b.spranger@linutronix.de, linux-can@vger.kernel.org
Subject: Re: [PATCH 05/16] c_can: use 32 bit access for D_CAN
Date: Sun, 24 Nov 2013 20:07:54 +0100 [thread overview]
Message-ID: <52924E8A.3070601@pengutronix.de> (raw)
In-Reply-To: <CAF03EBcKxO_JckT9BtxbHwax5o4rsQ1P+5X3ox_oJ_U+PPrLWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On 11/16/2013 05:37 PM, T Thayer wrote:
> What is the status of this patch?
The mail you copied reflects the current status, nothing happened since
then. Feel free to adopt this patch and address my comments.
> This fixes the problem I was seeing for the D_CAN portion of the
> driver which was
> 1. Transmitting 2 copies (probably the result of an AutoRetry)
> 2. Triggering a RX IRQ on a transmit because the Message Object # was
> assigned to RX.
> 3. CAN statistics were not incrementing properly.
>
> I just joined this mailing list and I don't have this email in my
> history so I'm copying it below.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2013-11-24 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 16:37 [PATCH 05/16] c_can: use 32 bit access for D_CAN T Thayer
2013-11-24 19:07 ` Marc Kleine-Budde [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-09 7:24 [PATCH 00/16] Support for Eberspächer Flexcard DCAN function Benedikt Spranger
2013-09-09 7:25 ` [PATCH 05/16] c_can: use 32 bit access for D_CAN Benedikt Spranger
2013-09-09 9:37 ` Marc Kleine-Budde
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=52924E8A.3070601@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=b.spranger@linutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=tthayer.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.