From: Greg KH <gregkh@linuxfoundation.org>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, stable@vger.kernel.org
Subject: Re: [PATCH 2/4] clk: agilex/stratix10: fix bypass representation
Date: Wed, 9 Jun 2021 20:58:22 +0200 [thread overview]
Message-ID: <YMEPToY4/q7UMsOO@kroah.com> (raw)
In-Reply-To: <20210609185008.36056-2-dinguyen@kernel.org>
On Wed, Jun 09, 2021 at 01:50:06PM -0500, Dinh Nguyen wrote:
> Each of these clocks(s2f_usr0/1, sdmmc_clk, gpio_db, emac_ptp,
> emac0/1/2) have a bypass setting that can use the boot_clk. The
> previous representation was not correct.
>
> Fix the representation.
>
> Fixes: 80c6b7a0894f ("clk: socfpga: agilex: add clock driver for the Agilex platform")
> Signed-off-by: Dinh Nguyen <dinguyen@kernel.org>
> ---
> drivers/clk/socfpga/clk-agilex.c | 57 ++++++++++++++++++++++++++------
> drivers/clk/socfpga/clk-s10.c | 55 ++++++++++++++++++++++++------
> 2 files changed, 91 insertions(+), 21 deletions(-)
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2021-06-09 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 18:50 [PATCH 1/4] clk: agilex/stratix10: remove noc_clk Dinh Nguyen
2021-06-09 18:50 ` [PATCH 2/4] clk: agilex/stratix10: fix bypass representation Dinh Nguyen
2021-06-09 18:58 ` Greg KH [this message]
2021-06-09 18:50 ` [PATCH 3/4] clk: agilex/stratix10: add support for the 2nd bypass Dinh Nguyen
2021-06-09 18:58 ` Greg KH
2021-06-09 18:50 ` [PATCH 4/4] clk: agilex/stratix10/n5x: fix how the bypass_reg is handled Dinh Nguyen
2021-06-09 18:58 ` Greg KH
2021-06-09 18:57 ` [PATCH 1/4] clk: agilex/stratix10: remove noc_clk Greg KH
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=YMEPToY4/q7UMsOO@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dinguyen@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=stable@vger.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.