From: Dan Murphy <dmurphy@ti.com>
To: <wg@grandegger.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 v12 1/5] can: m_can: Create a m_can platform framework
Date: Thu, 6 Jun 2019 08:16:37 -0500 [thread overview]
Message-ID: <93530d94-ec65-de82-448e-f2460dd39fb9@ti.com> (raw)
In-Reply-To: <a8e3f2d3-18c3-3bdb-1318-8964afc7e032@ti.com>
Marc
Bump
On 5/31/19 6:51 AM, Dan Murphy wrote:
> Marc
>
> On 5/15/19 3:54 PM, Dan Murphy wrote:
>> Marc
>>
>> On 5/9/19 11:11 AM, Dan Murphy wrote:
>>> Create a m_can platform framework that peripheral
>>> devices can register to and use common code and register sets.
>>> The peripheral devices may provide read/write and configuration
>>> support of the IP.
>>>
>>> Acked-by: Wolfgang Grandegger <wg@grandegger.com>
>>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>>> ---
>>>
>>> v12 - Update the m_can_read/write functions to create a backtrace if
>>> the callback
>>> pointer is NULL. - https://lore.kernel.org/patchwork/patch/1052302/
>>>
>> Is this able to be merged now?
>
> ping
>
>
>> Dan
>>
>> <snip>
next prev parent reply other threads:[~2019-06-06 13:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 16:11 [PATCH v12 1/5] can: m_can: Create a m_can platform framework Dan Murphy
2019-05-09 16:11 ` [PATCH v12 2/5] can: m_can: Rename m_can_priv to m_can_classdev Dan Murphy
2019-06-25 9:23 ` Faiz Abbas
2019-05-09 16:11 ` [PATCH v12 3/5] dt-bindings: can: tcan4x5x: Add DT bindings for TCAN4x5X driver Dan Murphy
2019-08-16 9:38 ` Marc Kleine-Budde
2019-08-22 14:20 ` Dan Murphy
2019-08-22 15:46 ` Marc Kleine-Budde
2019-08-22 15:58 ` Dan Murphy
2019-05-09 16:11 ` [PATCH v12 4/5] can: tcan4x5x: Add tcan4x5x driver to the kernel Dan Murphy
2019-05-09 16:11 ` [PATCH v12 5/5] can: m_can: Fix checkpatch issues on existing code Dan Murphy
2019-06-25 9:24 ` Faiz Abbas
2019-05-15 20:54 ` [PATCH v12 1/5] can: m_can: Create a m_can platform framework Dan Murphy
2019-05-31 11:51 ` Dan Murphy
2019-06-06 13:16 ` Dan Murphy [this message]
2019-06-10 16:35 ` Dan Murphy
2019-06-17 15:09 ` Dan Murphy
2019-07-10 12:08 ` Dan Murphy
2019-07-23 15:14 ` Dan Murphy
2019-07-24 6:47 ` Greg KH
2019-07-24 15:36 ` Dan Murphy
2019-07-25 6:28 ` Greg KH
2019-07-25 7:09 ` Marc Kleine-Budde
2019-07-16 18:23 ` Dan Murphy
2019-05-23 20:18 ` Dan Murphy
2019-06-25 9:22 ` Faiz Abbas
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=93530d94-ec65-de82-448e-f2460dd39fb9@ti.com \
--to=dmurphy@ti.com \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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).