From: Benoît <benoit@pouic.eu>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH] can: mcp251x: avoid repeated frame bug
Date: Mon, 03 Sep 2012 20:09:48 +0200 [thread overview]
Message-ID: <5044F26C.1070701@pouic.eu> (raw)
In-Reply-To: <5044F018.50808@pengutronix.de>
On 09/03/2012 07:59 PM, Marc Kleine-Budde wrote:
>> By the way, about using spi_write()instead of mcp251x_spi_trans(): I
>> innocently thought it would make less function call nesting,
>> trying to improve response time of the driver particularly on my
>> Raspberry Pi.
> Ahh, I see. but the mcp251x_spi_trans() function takes does the setup
> thats needed for DMA.
Very good argument indeed.
Best Regards,
Benoît.
next prev parent reply other threads:[~2012-09-03 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 12:17 [PATCH] can: mcp251x: avoid repeated frame bug Marc Kleine-Budde
2012-09-03 17:13 ` Benoît
2012-09-03 17:59 ` Marc Kleine-Budde
2012-09-03 18:09 ` Benoît [this message]
2012-09-05 19:59 ` Marc Kleine-Budde
-- strict thread matches above, loose matches on Subject: below --
2012-09-04 20:55 pull-request: can 2012-09-04 Marc Kleine-Budde
2012-09-04 20:55 ` [PATCH] can: mcp251x: avoid repeated frame bug 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=5044F26C.1070701@pouic.eu \
--to=benoit@pouic.eu \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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