From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: renesas: r8a779f0: Add HSCIF0+1 clocks
Date: Mon, 13 Jun 2022 22:04:53 +0200 [thread overview]
Message-ID: <YqeYZXTDmW7rfgCP@shikoro> (raw)
In-Reply-To: <20220613130949.10001-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
On Mon, Jun 13, 2022 at 03:09:49PM +0200, Wolfram Sang wrote:
> Those have been successfully tested. HSCIF2+3 still need verification.
I managed to test all other HSCIFs and SCIFs now. I'll resend the
updated patches tomorrow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-06-13 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 13:09 [PATCH] clk: renesas: r8a779f0: Add HSCIF0+1 clocks Wolfram Sang
2022-06-13 20:04 ` Wolfram Sang [this message]
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=YqeYZXTDmW7rfgCP@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox