From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Brian Masney <bmasney@redhat.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Bouncing email for Renesas Versaclock 7 Clock Driver maintainer
Date: Fri, 29 Aug 2025 15:21:54 +0200 [thread overview]
Message-ID: <CAMuHMdXkrx7DRrCBe7uKLrxFOnwhbVwtetC-VVbsW-61SwvvyQ@mail.gmail.com> (raw)
In-Reply-To: <CABx5tqJ0+1bjoMM4qPS94coa0wyQaae1gJP14pUKk+xVgD5kaQ@mail.gmail.com>
Hi Brian,
On Fri, 29 Aug 2025 at 13:25, Brian Masney <bmasney@redhat.com> wrote:
> The MAINTAINERS file has the following entry and Alex's email address bounces.
>
> RENESAS VERSACLOCK 7 CLOCK DRIVER
> M: Alex Helms <alexander.helms.jy@renesas.com>
> S: Maintained
> F: Documentation/devicetree/bindings/clock/renesas,versaclock7.yaml
> F: drivers/clk/clk-versaclock7.c
>
> Should this driver, along with clk-versaclock3.c and clk-versaclock5.c
> be moved under the drivers/clk/renesas/ directory?
The latter is meant for on-SoC clock drivers.
The versaclock parts are "discrete" clock controllers.
> If not, is there anyone else from Renesas that should be listed as a
> maintainer instead?
Checking internally...
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
next prev parent reply other threads:[~2025-08-29 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 11:24 Bouncing email for Renesas Versaclock 7 Clock Driver maintainer Brian Masney
2025-08-29 13:21 ` Geert Uytterhoeven [this message]
2025-09-05 10:47 ` Biju Das
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=CAMuHMdXkrx7DRrCBe7uKLrxFOnwhbVwtetC-VVbsW-61SwvvyQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bmasney@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).