From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 1/3] clk: renesas: r8a7795: Add RPC clocks
Date: Mon, 10 Feb 2020 15:17:12 +0100 [thread overview]
Message-ID: <CAMuHMdVNasuQW=TcnaSZ6wcnB73+dhD4w1e4iBYB2WtCtp-ndw@mail.gmail.com> (raw)
In-Reply-To: <20200203072901.31548-1-dirk.behme@de.bosch.com>
On Mon, Feb 3, 2020 at 8:29 AM Dirk Behme <dirk.behme@de.bosch.com> wrote:
> Describe the RPCSRC internal clock and the RPC[D2] clocks derived from it,
> as well as the RPC-IF module clock, in the R-Car H3 (R8A7795) CPG/MSSR
> driver.
>
> Inspired by commit 94e3935b5756 ("clk: renesas: r8a77980: Add RPC clocks").
>
> Signed-off-by: Dirk Behme <dirk.behme@de.bosch.com>
Thanks, all 3 queued in clk-renesas-for-v5.7.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2020-02-10 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 7:28 [PATCH 1/3] clk: renesas: r8a7795: Add RPC clocks Dirk Behme
2020-02-03 7:29 ` [PATCH 2/3] clk: renesas: r8a7796: " Dirk Behme
2020-02-06 15:47 ` Geert Uytterhoeven
2020-02-07 5:19 ` Behme Dirk (CM/ESO2)
2020-02-03 7:29 ` [PATCH 3/3] clk: renesas: r8a77965: " Dirk Behme
2020-02-06 15:47 ` Geert Uytterhoeven
2020-02-06 15:46 ` [PATCH 1/3] clk: renesas: r8a7795: " Geert Uytterhoeven
2020-02-10 14:17 ` Geert Uytterhoeven [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='CAMuHMdVNasuQW=TcnaSZ6wcnB73+dhD4w1e4iBYB2WtCtp-ndw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dirk.behme@de.bosch.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).