linux-kernel - Re: [RESEND PATCH v4] MAINTAINERS: add polarfire rng, pci and clock drivers

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 7 Jul 2022 13:30:27 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <palmer@...osinc.com>, <palmer@...belt.com>, <arnd@...db.de>
CC:     <Conor.Dooley@...rochip.com>, <Cyril.Jean@...rochip.com>,
        <Daire.McNamara@...rochip.com>, <Lewis.Hanly@...rochip.com>,
        <aou@...s.berkeley.edu>, <gregkh@...uxfoundation.org>,
        <herbert@...dor.apana.org.au>, <kw@...ux.com>,
        <linux-clk@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-pci@...r.kernel.org>, <linux-riscv@...ts.infradead.org>,
        <lorenzo.pieralisi@....com>, <mturquette@...libre.com>,
        <paul.walmsley@...ive.com>, <robh@...nel.org>,
        <bhelgaas@...gle.com>, <sboyd@...nel.org>, <wsa@...nel.org>
Subject: Re: [RESEND PATCH v4] MAINTAINERS: add polarfire rng, pci and clock
 drivers

On 22/06/2022 23:58, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@...rochip.com>
> 
> Hardware random, PCI and clock drivers for the PolarFire SoC have been
> upstreamed but are not covered by the MAINTAINERS entry, so add them.
> Daire is the author of the clock & PCI drivers, so add him as a
> maintainer in place of Lewis.
> 
> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
> Acked-by: Stephen Boyd <sboyd@...nel.org>
> Signed-off-by: Conor Dooley <conor.dooley@...rochip.com>

Arnd, Palmer:
Does the SoC tree make more sense for this patch?
I am missing an ack from Herbert (but I don't think that's blocking
for a MAINTAINERS update to my own entry?).

If SoC is the better option, should I resend this to soc@...nel.org?
Unfortunately, since I originally sent this patch there have been
other changes to this entry that will conflict in -next (all are
additions so easily resolved...).

I was hoping to get this patch applied to v5.19-rc(foo) since we
never added maintainers entries for these drivers rather than wait
for v5.20.

If you (plural) would rather wait for v5.20, I can resubmit this patch
after v5.20-mw1 with an additional i2c entry (if the driver is applied)
that already has an ack from Wolfram.

Thanks,
Conor.

> ---
>   MAINTAINERS | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a6d3bd9d2a8d..01a7bfa49bdc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17136,12 +17136,15 @@ N:	riscv
>   K:	riscv
>   
>   RISC-V/MICROCHIP POLARFIRE SOC SUPPORT
> -M:	Lewis Hanly <lewis.hanly@...rochip.com>
>   M:	Conor Dooley <conor.dooley@...rochip.com>
> +M:	Daire McNamara <daire.mcnamara@...rochip.com>
>   L:	linux-riscv@...ts.infradead.org
>   S:	Supported
>   F:	arch/riscv/boot/dts/microchip/
> +F:	drivers/char/hw_random/mpfs-rng.c
> +F:	drivers/clk/microchip/clk-mpfs.c
>   F:	drivers/mailbox/mailbox-mpfs.c
> +F:	drivers/pci/controller/pcie-microchip-host.c
>   F:	drivers/soc/microchip/
>   F:	include/soc/microchip/mpfs.h
>