All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: mturquette@baylibre.com
Cc: sboyd@codeaurora.org, linux-clk@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	Xing Zheng <zhengxing@rock-chips.com>
Subject: Re: [PATCH] clk: rockchip: fix rk3368 cpuclk divider offsets
Date: Thu, 03 Dec 2015 16:47:31 +0100	[thread overview]
Message-ID: <3718967.dRZrdSmclK@diego> (raw)
In-Reply-To: <6481456.ejZyd6DyuY@diego>

Am Dienstag, 1. Dezember 2015, 22:31:56 schrieb Heiko St=FCbner:
> Due to a copy-paste error the the rk3368 cpuclk settings were acessin=
g
> rk3288-specific register offsets. This never caused problems till now=
,
> as cpu frequency scaling in't used currently at all.
>=20
> Reported-by: Xing Zheng <zhengxing@rock-chips.com>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>

applied to my clock-branch for 4.5

WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: mturquette@baylibre.com
Cc: sboyd@codeaurora.org, linux-clk@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	Xing Zheng <zhengxing@rock-chips.com>
Subject: Re: [PATCH] clk: rockchip: fix rk3368 cpuclk divider offsets
Date: Thu, 03 Dec 2015 16:47:31 +0100	[thread overview]
Message-ID: <3718967.dRZrdSmclK@diego> (raw)
In-Reply-To: <6481456.ejZyd6DyuY@diego>

Am Dienstag, 1. Dezember 2015, 22:31:56 schrieb Heiko Stübner:
> Due to a copy-paste error the the rk3368 cpuclk settings were acessing
> rk3288-specific register offsets. This never caused problems till now,
> as cpu frequency scaling in't used currently at all.
> 
> Reported-by: Xing Zheng <zhengxing@rock-chips.com>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>

applied to my clock-branch for 4.5

  reply	other threads:[~2015-12-03 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 21:31 [PATCH] clk: rockchip: fix rk3368 cpuclk divider offsets Heiko Stübner
2015-12-03 15:47 ` Heiko Stübner [this message]
2015-12-03 15:47   ` Heiko Stübner

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=3718967.dRZrdSmclK@diego \
    --to=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=zhengxing@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.