From: Troy Mitchell <troy.mitchell@linux.dev>
To: Xuyang Dong <dongxuyang@eswincomputing.com>,
Troy Mitchell <troy.mitchell@linux.dev>,
mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, bmasney@redhat.com,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
huangyifeng@eswincomputing.com, pinkesh.vaghela@einfochips.com
Subject: Re: Re: [PATCH v7 2/2] clock: eswin: Add eic7700 clock driver
Date: Tue, 11 Nov 2025 11:38:40 +0800 [thread overview]
Message-ID: <aRKvwL-puEquiIOh@kernel.org> (raw)
In-Reply-To: <74be57c4.45.19a7080fca1.Coremail.dongxuyang@eswincomputing.com>
On Tue, Nov 11, 2025 at 09:21:32AM +0800, Xuyang Dong wrote:
> Hi Troy,
>
> The link [1] provides the official documentation for the EIC7700.
> Section 3.2 covers the clock subsystem, where you can find detailed
> information about the clock-tree.
Much clearer now. I suggest putting this link directly in the cover-letter
in the next version.
>
> [1] https://www.sifive.com/document-file/eic7700x-datasheet
Thanks for your link.
- Troy
>
> Regards,
> Xuyang Dong
next prev parent reply other threads:[~2025-11-11 3:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 7:16 [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller dongxuyang
2025-10-23 7:17 ` [PATCH v7 1/2] dt-bindings: clock: eswin: Documentation for eic7700 SoC dongxuyang
2025-11-07 7:46 ` Troy Mitchell
2025-10-23 7:18 ` [PATCH v7 2/2] clock: eswin: Add eic7700 clock driver dongxuyang
2025-11-07 7:44 ` Troy Mitchell
2025-11-11 1:21 ` Xuyang Dong
2025-11-11 3:38 ` Troy Mitchell [this message]
2025-11-06 7:57 ` [PATCH v7 0/2] Add driver support for ESWIN eic700 SoC clock controller Xuyang Dong
2025-11-06 8:20 ` Krzysztof Kozlowski
2025-11-07 6:20 ` Xuyang Dong
2025-11-07 7:04 ` Krzysztof Kozlowski
2025-11-07 7:35 ` Troy Mitchell
2025-11-07 9:02 ` Xuyang Dong
2025-11-07 10:05 ` Troy Mitchell
2025-11-07 15:54 ` Troy Mitchell
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=aRKvwL-puEquiIOh@kernel.org \
--to=troy.mitchell@linux.dev \
--cc=bmasney@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongxuyang@eswincomputing.com \
--cc=huangyifeng@eswincomputing.com \
--cc=krzk+dt@kernel.org \
--cc=linmin@eswincomputing.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ningyu@eswincomputing.com \
--cc=pinkesh.vaghela@einfochips.com \
--cc=robh@kernel.org \
--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 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).