From: Dan Murphy <dmurphy@ti.com>
To: <linux-kernel@vger.kernel.org>, <mkl@pengutronix.de>,
<linux-can@vger.kernel.org>, <wg@grandegger.com>,
<sriram.dash@samsung.com>
Cc: <davem@davemloft.net>
Subject: Re: [PATCH linux-master 0/3] MCAN updates for clock discovery
Date: Wed, 19 Feb 2020 07:07:19 -0600 [thread overview]
Message-ID: <a97ed7ef-e95a-af32-4d01-2ed7c2c08c20@ti.com> (raw)
In-Reply-To: <20200131183433.11041-1-dmurphy@ti.com>
Bump
On 1/31/20 12:34 PM, Dan Murphy wrote:
> Hello
>
> These are the initial fixes for issues found in and requested in
> https://lore.kernel.org/patchwork/patch/1165091/
>
> For the clock discovery and initialization.
>
> Dan
>
> Dan Murphy (3):
> can: tcan4x5x: Move clock init to TCAN driver
> can: m_can_platform: Move clock discovery and init to platform
> can: m_can: Remove unused clock function from the framework
>
> drivers/net/can/m_can/m_can.c | 16 ------
> drivers/net/can/m_can/m_can.h | 3 -
> drivers/net/can/m_can/m_can_platform.c | 37 +++++++++---
> drivers/net/can/m_can/tcan4x5x.c | 78 +++++++++++++++++++-------
> 4 files changed, 89 insertions(+), 45 deletions(-)
>
prev parent reply other threads:[~2020-02-19 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 18:34 [PATCH linux-master 0/3] MCAN updates for clock discovery Dan Murphy
2020-01-31 18:34 ` [PATCH linux-master 1/3] can: tcan4x5x: Move clock init to TCAN driver Dan Murphy
2020-02-21 14:25 ` Dan Murphy
2020-02-21 14:43 ` Marc Kleine-Budde
2020-02-25 17:45 ` Dan Murphy
2020-02-25 20:48 ` Marc Kleine-Budde
2020-01-31 18:34 ` [PATCH linux-master 2/3] can: m_can_platform: Move clock discovery and init to platform Dan Murphy
2020-01-31 18:34 ` [PATCH linux-master 3/3] can: m_can: Remove unused clock function from the framework Dan Murphy
2020-02-19 13:07 ` Dan Murphy [this message]
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=a97ed7ef-e95a-af32-4d01-2ed7c2c08c20@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=sriram.dash@samsung.com \
--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).