From: Tony Lindgren <tony@atomide.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: kernel@pengutronix.de, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-can@vger.kernel.org,
Faiz Abbas <faiz_abbas@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: dra76x: m_can: fix order of clocks
Date: Thu, 19 Nov 2020 11:38:11 +0200 [thread overview]
Message-ID: <20201119093811.GJ26857@atomide.com> (raw)
In-Reply-To: <20201111141211.1577871-1-mkl@pengutronix.de>
* Marc Kleine-Budde <mkl@pengutronix.de> [201111 16:12]:
> According to the bosch,m_can.yaml bindings the first clock shall be the "hclk",
> while the second clock "cclk".
>
> This patch fixes the order accordingly.
Thanks applying into fixes.
Tony
prev parent reply other threads:[~2020-11-19 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 14:12 [PATCH] ARM: dts: dra76x: m_can: fix order of clocks Marc Kleine-Budde
2020-11-19 9:38 ` Tony Lindgren [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=20201119093811.GJ26857@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=robh+dt@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).