From: Moritz Fischer <mdf@kernel.org>
To: trix@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [PATCH v2] MAINTAINERS: Add FPGA SUBDEVICES
Date: Fri, 22 Jan 2021 15:52:37 -0800 [thread overview]
Message-ID: <YAtlRV+0FWrVoaRc@archbook> (raw)
In-Reply-To: <20210122192928.1651254-1-trix@redhat.com>
On Fri, Jan 22, 2021 at 11:29:28AM -0800, trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.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@redhat.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@redhat.com>
> +L: linux-fpga@vger.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@melbpc.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
next prev parent reply other threads:[~2021-01-22 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:29 [PATCH v2] MAINTAINERS: Add FPGA SUBDEVICES trix
2021-01-22 23:52 ` Moritz Fischer [this message]
2021-01-23 15:01 ` Tom Rix
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=YAtlRV+0FWrVoaRc@archbook \
--to=mdf@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trix@redhat.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).