From: Krzysztof Kozlowski <krzk@kernel.org>
To: dongxuyang@eswincomputing.com, mturquette@baylibre.com,
sboyd@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ningyu@eswincomputing.com, linmin@eswincomputing.com,
huangyifeng@eswincomputing.com
Subject: Re: [PATCH v2 2/2] clock: eswin: Add eic7700 clock driver
Date: Fri, 23 May 2025 11:13:50 +0200 [thread overview]
Message-ID: <8752f974-473d-4bb6-9c00-e9a79f905bfe@kernel.org> (raw)
In-Reply-To: <20250523090928.1940-1-dongxuyang@eswincomputing.com>
On 23/05/2025 11:09, dongxuyang@eswincomputing.com wrote:
> From: Xuyang Dong <dongxuyang@eswincomputing.com>
>
> This driver depends on the CCF framework implementation.
> Based on this driver, other modules in the SoC can use the APIs
> provided by CCF to perform clock-related operations.
> The driver supports eic7700 series chips.
>
> Signed-off-by: Yifeng Huang <huangyifeng@eswincomputing.com>
> Signed-off-by: Xuyang Dong <dongxuyang@eswincomputing.com>
> Reviewed-by: Krzysztof Kozlowski <krzk+dt@kernel.org>
NAK, stop adding fake tags. How did you even invent such email?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-23 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 9:07 [PATCH v2 0/2] Add driver support for ESWIN eic700 SoC clock controller dongxuyang
2025-05-23 9:09 ` [PATCH v2 1/2] dt-bindings: clock: eswin: Documentation for eic7700 SoC dongxuyang
2025-05-23 9:11 ` Krzysztof Kozlowski
2025-05-23 9:09 ` [PATCH v2 2/2] clock: eswin: Add eic7700 clock driver dongxuyang
2025-05-23 9:13 ` Krzysztof Kozlowski [this message]
2025-05-23 9:16 ` Krzysztof Kozlowski
2025-05-23 9:11 ` [PATCH v2 0/2] Add driver support for ESWIN eic700 SoC clock controller Krzysztof Kozlowski
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=8752f974-473d-4bb6-9c00-e9a79f905bfe@kernel.org \
--to=krzk@kernel.org \
--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=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