linux-kernel - Re: [PATCH v2] MAINTAINERS: Add FPGA SUBDEVICES

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:   Fri, 22 Jan 2021 15:52:37 -0800
From:   Moritz Fischer <mdf@...nel.org>
To:     trix@...hat.com
Cc:     linux-kernel@...r.kernel.org, linux-fpga@...r.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Add FPGA SUBDEVICES

On Fri, Jan 22, 2021 at 11:29:28AM -0800, trix@...hat.com wrote:
> From: Tom Rix <trix@...hat.com>
> 
> Every FPGA has several subdevices in other subsystems.
> The new FPGA subdevices section is necessary to ensure changes to
> the subdevices files get reviewed within the context of the FPGA
> subsystem.
> 
> Signed-off-by: Tom Rix <trix@...hat.com>
> ---
> v1: Add several more subdevices
> ---
>  MAINTAINERS | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 17ac5bdce521..96d6f00b0584 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6975,6 +6975,17 @@ F:	drivers/fpga/
>  F:	include/linux/fpga/
>  F:	tools/testing/selftests/drivers/fpga/
>  
> +FPGA SUBDEVICES
> +R:	Tom Rix <trix@...hat.com>
> +L:	linux-fpga@...r.kernel.org
> +S:	Maintained
> +F:	Documentation/ABI/testing/sysfs-driver-intel-m10-bmc
> +F:	Documentation/hwmon/intel-m10-bmc-hwmon.rst
> +F:	drivers/hwmon/intel-m10-bmc-hwmon.c
> +F:	drivers/memory/dfl-emif.c
> +F:	drivers/mfd/intel-m10-bmc.c
> +F:	include/linux/mfd/intel-m10-bmc.h
> +
>  FPU EMULATOR
>  M:	Bill Metzenthen <billm@...bpc.org.au>
>  S:	Maintained
> -- 
> 2.27.0
> 
All these subsystems have maintainers, I think that's up to them.
Ideally each of those drivers behaves like a normal device in the
corresponding subsystem and the way it's implemented doesn't matter.

Plenty of other examples for that

drivers/net/ethernet/xilinx/*

for example.

- Moritz