From: Tony Lindgren <tony@atomide.com>
To: Faiz Abbas <faiz_abbas@ti.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, vigneshr@ti.com, j-keerthy@ti.com,
lokeshvutla@ti.com, mark.rutland@arm.com, robh+dt@kernel.org,
bcousson@baylibre.com
Subject: Re: [PATCH] arm: dts: dra76x: Fix mmc3 max-frequency
Date: Wed, 26 Feb 2020 10:37:24 -0800 [thread overview]
Message-ID: <20200226183724.GX37466@atomide.com> (raw)
In-Reply-To: <20200128134759.21134-1-faiz_abbas@ti.com>
* Faiz Abbas <faiz_abbas@ti.com> [200128 05:47]:
> dra76x is not affected by i887 which requires mmc3 node to be limited to
> a max frequency of 64 MHz. Fix this by overwriting the correct value in
> the the dra76 specific dtsi.
>
> Fixes: 895bd4b3e5ec ("ARM: dts: Add support for dra76-evm")
Sorry looks like I missed this earlier, applying into fixes.
Thanks,
Tony
prev parent reply other threads:[~2020-02-26 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 13:47 [PATCH] arm: dts: dra76x: Fix mmc3 max-frequency Faiz Abbas
2020-02-26 18:37 ` 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=20200226183724.GX37466@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).