linux-kernel - Re: Bouncing email for Renesas Versaclock 7 Clock Driver maintainer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMuHMdXkrx7DRrCBe7uKLrxFOnwhbVwtetC-VVbsW-61SwvvyQ@mail.gmail.com>
Date: Fri, 29 Aug 2025 15:21:54 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Brian Masney <bmasney@...hat.com>
Cc: Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, 
	linux-renesas-soc@...r.kernel.org, linux-clk@...r.kernel.org, 
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Bouncing email for Renesas Versaclock 7 Clock Driver maintainer

Hi Brian,

On Fri, 29 Aug 2025 at 13:25, Brian Masney <bmasney@...hat.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@...esas.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@...ux-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