From: Conor Dooley <conor.dooley@microchip.com>
To: WangYuli <wangyuli@uniontech.com>
Cc: <stable@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<sashal@kernel.org>, <william.qiu@starfivetech.com>,
<emil.renner.berthing@canonical.com>,
<xingyu.wu@starfivetech.com>, <walker.chen@starfivetech.com>,
<robh@kernel.org>, <hal.feng@starfivetech.com>, <kernel@esmil.dk>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>,
<devicetree@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <richardcochran@gmail.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH 6.6 1/4] riscv: dts: starfive: add assigned-clock* to limit frquency
Date: Mon, 9 Sep 2024 11:17:58 +0100 [thread overview]
Message-ID: <20240909-fidgeting-baggage-e9ef9fab9ca4@wendy> (raw)
In-Reply-To: <D200DC520B462771+20240909074645.1161554-1-wangyuli@uniontech.com>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
On Mon, Sep 09, 2024 at 03:46:27PM +0800, WangYuli wrote:
> From: William Qiu <william.qiu@starfivetech.com>
>
> In JH7110 SoC, we need to go by-pass mode, so we need add the
> assigned-clock* properties to limit clock frquency.
>
> Signed-off-by: William Qiu <william.qiu@starfivetech.com>
> Reviewed-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
What makes any of the patches in this 4 patch series stable material?
Confused,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-09 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 7:46 [PATCH 6.6 1/4] riscv: dts: starfive: add assigned-clock* to limit frquency WangYuli
2024-09-09 10:17 ` Conor Dooley [this message]
2024-09-09 10:38 ` Krzysztof Kozlowski
2024-09-09 11:17 ` Conor Dooley
2024-09-12 2:38 ` WangYuli
2024-09-12 7:31 ` Conor Dooley
2024-09-09 17:04 ` 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=20240909-fidgeting-baggage-e9ef9fab9ca4@wendy \
--to=conor.dooley@microchip.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=hal.feng@starfivetech.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=walker.chen@starfivetech.com \
--cc=wangyuli@uniontech.com \
--cc=william.qiu@starfivetech.com \
--cc=xingyu.wu@starfivetech.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