All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	linux-stable@vger.kernel.org
Subject: Re: [PATCH] clk: uniphier: Fix update register for CPU-gear
Date: Fri, 8 Feb 2019 11:31:30 +0900	[thread overview]
Message-ID: <CAK7LNATMCT74HKroyR-Sx2pm7vVWzuNb2fRbDtCSQvKViszo=g@mail.gmail.com> (raw)
In-Reply-To: <1549592723-18494-1-git-send-email-hayashi.kunihiko@socionext.com>

On Fri, Feb 8, 2019 at 11:25 AM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
>
> Need to set the update bit in UNIPHIER_CLK_CPUGEAR_UPD to update
> the CPU-gear value.
>
> Fixes: d08f1f0d596c ("clk: uniphier: add CPU-gear change (cpufreq) support")
> Cc: linux-stable@vger.kernel.org
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---


Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>


-- 
Best Regards
Masahiro Yamada

WARNING: multiple messages have this Message-ID (diff)
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: linux-stable@vger.kernel.org,
	Masami Hiramatsu <masami.hiramatsu@linaro.org>,
	Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] clk: uniphier: Fix update register for CPU-gear
Date: Fri, 8 Feb 2019 11:31:30 +0900	[thread overview]
Message-ID: <CAK7LNATMCT74HKroyR-Sx2pm7vVWzuNb2fRbDtCSQvKViszo=g@mail.gmail.com> (raw)
In-Reply-To: <1549592723-18494-1-git-send-email-hayashi.kunihiko@socionext.com>

On Fri, Feb 8, 2019 at 11:25 AM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
>
> Need to set the update bit in UNIPHIER_CLK_CPUGEAR_UPD to update
> the CPU-gear value.
>
> Fixes: d08f1f0d596c ("clk: uniphier: add CPU-gear change (cpufreq) support")
> Cc: linux-stable@vger.kernel.org
> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
> ---


Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>


-- 
Best Regards
Masahiro Yamada

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-08  2:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08  2:25 [PATCH] clk: uniphier: Fix update register for CPU-gear Kunihiko Hayashi
2019-02-08  2:25 ` Kunihiko Hayashi
2019-02-08  2:31 ` Masahiro Yamada [this message]
2019-02-08  2:31   ` Masahiro Yamada
2019-02-21 21:50 ` Stephen Boyd
2019-02-21 21:50   ` Stephen Boyd

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='CAK7LNATMCT74HKroyR-Sx2pm7vVWzuNb2fRbDtCSQvKViszo=g@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stable@vger.kernel.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@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 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.