From: Marek Vasut <marex@denx.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH V4 1/4] net: can: ifi: Fix clock generator configuration
Date: Thu, 03 Mar 2016 22:29:48 +0100 [thread overview]
Message-ID: <56D8ACCC.1020805@denx.de> (raw)
In-Reply-To: <56D8A744.4030109@hartkopp.net>
On 03/03/2016 10:06 PM, Oliver Hartkopp wrote:
>
>
> On 03/03/2016 10:05 PM, Marc Kleine-Budde wrote:
>
>>> Reviewed-by: Oliver Hartkopp <socketcan@hartkopp.net>
>>>
>>> finally seems appropriate :)
>>
>> For all four patches?
>
> yep.
>
Whew, thank you :-)
In case I detect some more defects, I will send subsequent patches. I'm
sure there is considerable amount of real-world testing coming for this
driver.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-03-03 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 19:45 [PATCH V4 0/4] Synchronise IFI CANFD driver with real world Marek Vasut
2016-03-03 19:45 ` [PATCH V4 1/4] net: can: ifi: Fix clock generator configuration Marek Vasut
2016-03-03 20:18 ` Oliver Hartkopp
2016-03-03 20:52 ` Marek Vasut
2016-03-03 20:58 ` Oliver Hartkopp
2016-03-03 21:01 ` Marc Kleine-Budde
2016-03-03 21:02 ` Marc Kleine-Budde
2016-03-03 21:04 ` Oliver Hartkopp
2016-03-03 21:05 ` Marc Kleine-Budde
2016-03-03 21:06 ` Oliver Hartkopp
2016-03-03 21:29 ` Marek Vasut [this message]
2016-03-03 19:45 ` [PATCH V4 2/4] net: can: ifi: Fix TX DLC configuration Marek Vasut
2016-03-03 19:45 ` [PATCH V4 3/4] net: can: ifi: Fix RX and TX ID mask Marek Vasut
2016-03-03 19:45 ` [PATCH V4 4/4] net: can: ifi: Add obscure bit swap for EFF frame IDs Marek Vasut
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=56D8ACCC.1020805@denx.de \
--to=marex@denx.de \
--cc=linux-can@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--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).