From: Wolfgang Grandegger <wg@grandegger.com>
To: Dan Murphy <dmurphy@ti.com>, mkl@pengutronix.de, davem@davemloft.net
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] can: m_can: Create a m_can platform framework
Date: Fri, 18 Jan 2019 07:56:24 +0100 [thread overview]
Message-ID: <641ae2ce-def9-6032-b8dc-cc71311bc993@grandegger.com> (raw)
In-Reply-To: <aa72c1a7-ee16-dbde-0b75-96f9632ec431@ti.com>
Hello Dan,
Am 17.01.19 um 21:08 schrieb Dan Murphy:
> Wolfgang
>
> On 1/17/19 2:05 PM, Dan Murphy wrote:
>> Create a m_can platform framework that peripherial
>> devices can register to and use common code and register sets.
>> The peripherial devices may provide read/write and configuration
>> support of the IP.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>> drivers/net/can/m_can/m_can.c | 6 +
>> drivers/net/can/m_can/m_can_platform.c | 209 +++++++++++++++++++++++++
>> drivers/net/can/m_can/m_can_platform.h | 163 +++++++++++++++++++
>> 3 files changed, 378 insertions(+)
>> create mode 100644 drivers/net/can/m_can/m_can_platform.c
>> create mode 100644 drivers/net/can/m_can/m_can_platform.h
>>
... snip ...
> This patch set is working for the TCAN and at least boots on io-mapped devices.
> We have a couple of customers who are looking at using this implementation and we would like to
> start moving this patch set along in the review.
>
> I did not put a change log in here as there have been no comments for the last 3 patch sets I sent.
>
> This v4 squashes a few bugs I found during testing across all the files.
OK, after a very busy week I will try to find time for the review...
finally.
Thanks,
Wolfgang.
next prev parent reply other threads:[~2019-01-18 6:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 20:05 [PATCH v4 1/4] can: m_can: Create a m_can platform framework Dan Murphy
2019-01-17 20:05 ` [PATCH v4 2/4] can: m_can: Migrate the m_can code to use the framework Dan Murphy
2019-01-22 9:35 ` Wolfgang Grandegger
2019-01-22 13:37 ` Dan Murphy
2019-01-22 14:34 ` Wolfgang Grandegger
2019-01-17 20:06 ` [PATCH v4 3/4] dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver Dan Murphy
2019-01-17 20:06 ` [PATCH v4 4/4] can: tcan4x5x: Add tcan4x5x driver to the kernel Dan Murphy
2019-01-22 10:03 ` Wolfgang Grandegger
2019-01-29 19:27 ` Dan Murphy
2019-01-17 20:08 ` [PATCH v4 1/4] can: m_can: Create a m_can platform framework Dan Murphy
2019-01-18 6:56 ` Wolfgang Grandegger [this message]
2019-01-18 12:55 ` Dan Murphy
2019-01-22 8:16 ` Wolfgang Grandegger
2019-01-22 13:04 ` Dan Murphy
2019-01-22 14:46 ` 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=641ae2ce-def9-6032-b8dc-cc71311bc993@grandegger.com \
--to=wg@grandegger.com \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.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).