From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: dts: sunxi: Unify the DE2 bus clocks order
Date: Mon, 22 Jul 2019 16:50:41 +0200 [thread overview]
Message-ID: <20190722145041.fc5gep5jialgcaea@flea> (raw)
In-Reply-To: <CAGb2v67QRQ4748U00o+V=-L06KEb5qwCraZD_V0CO-JT18yk9g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 744 bytes --]
On Mon, Jul 22, 2019 at 10:16:07PM +0800, Chen-Yu Tsai wrote:
> On Mon, Jul 22, 2019 at 10:08 PM Maxime Ripard
> <maxime.ripard@bootlin.com> wrote:
> >
> > The DE2 bus takes two clocks, named bus and mod according to the binding.
> >
> > However, the order of these clocks change from one SoC to another. Even
> > though it might not be an issue in most cases, having consistency will help
> > if we ever need to have some code to deal with deprecated bindings, and in
> > general it's just better.
> >
> > Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
>
> Acked-by: Chen-Yu Tsai <wens@csie.org>
>
> for both patches.
Applied both, thanks
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-22 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 14:08 [PATCH 1/2] ARM: dts: sunxi: Unify the DE2 bus clocks order Maxime Ripard
2019-07-22 14:08 ` [PATCH 2/2] arm64: dts: allwinner: h6: Fix SID node name Maxime Ripard
2019-07-22 14:16 ` [PATCH 1/2] ARM: dts: sunxi: Unify the DE2 bus clocks order Chen-Yu Tsai
2019-07-22 14:50 ` Maxime Ripard [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=20190722145041.fc5gep5jialgcaea@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=wens@csie.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).