linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] i.MX fixes for 4.19, round 2
Date: Tue, 2 Oct 2018 19:48:17 -0700	[thread overview]
Message-ID: <20181003024815.GA4398@X250> (raw)
In-Reply-To: <CAK8P3a0d3C3gDi_Ozh1gBTVXiAOc67_8SOYh7tzWVpP8trO8-A@mail.gmail.com>

On Tue, Oct 02, 2018 at 02:09:10PM +0200, Arnd Bergmann wrote:
> Shawn, should I cherry-pick the other fix, or do you want to
> follow up with a new pull request for the fixes?

Arnd, I just updated the pull request with the patch in question dropped.

Shawn


The following changes since commit 57361846b52bc686112da6ca5368d11210796804:

  Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-4.19-2

for you to fetch changes up to eea96566c189c77e5272585984eb2729881a2f1d:

  ARM: dts: imx53-qsb: disable 1.2GHz OPP (2018-09-12 14:44:33 +0800)

----------------------------------------------------------------
i.MX fixes for 4.19, round 2:
 - i.MX53 QSB board stops working when cpufreq driver is enabled,
   because the default OPP table has the maximum CPU frequency at
   1.2GHz, while the board is only capable of running 1GHz.  Fix up
   the OPP table for the board to get it work with cpufreq driver.

----------------------------------------------------------------
Sascha Hauer (1):
      ARM: dts: imx53-qsb: disable 1.2GHz OPP

 arch/arm/boot/dts/imx53-qsb-common.dtsi | 11 +++++++++++
 1 file changed, 11 insertions(+)

  reply	other threads:[~2018-10-03  2:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01  2:39 [GIT PULL] i.MX fixes for 4.19, round 2 Shawn Guo
2018-10-02  9:59 ` Arnd Bergmann
2018-10-02 11:42   ` Lucas Stach
2018-10-02 12:09     ` Arnd Bergmann
2018-10-03  2:48       ` Shawn Guo [this message]
2018-10-04 15:34         ` Arnd Bergmann
2018-12-17 16:42       ` Lucas Stach

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=20181003024815.GA4398@X250 \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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).