From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Dan Murphy <dmurphy@ti.com>,
linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
wg@grandegger.com, sriram.dash@samsung.com
Cc: davem@davemloft.net
Subject: Re: [PATCH linux-master 1/3] can: tcan4x5x: Move clock init to TCAN driver
Date: Fri, 21 Feb 2020 15:43:59 +0100 [thread overview]
Message-ID: <fed1d801-e284-eada-d5b3-ae78089b3ead@pengutronix.de> (raw)
In-Reply-To: <06af6e1d-aec4-189c-378a-77af4073a1a6@ti.com>
On 2/21/20 3:25 PM, Dan Murphy wrote:
> Hello
>
> On 1/31/20 12:34 PM, Dan Murphy wrote:
>> Move the clock discovery and initialization from the m_can framework to
>> the registrar. This allows for registrars to have unique clock
>> initialization. The TCAN device only needs the CAN clock reference.
>>
>> Signed-off-by: Dan Murphy <dmurphy@ti.com>
>> ---
>
> I would like to have these 3 patches reviewed and integrated (post
> review) so I can work on other issues identified.
Applied to linux-can-next/testing.
tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2020-02-21 14:44 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 [this message]
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 ` [PATCH linux-master 0/3] MCAN updates for clock discovery Dan Murphy
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=fed1d801-e284-eada-d5b3-ae78089b3ead@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®