From: Conor Dooley <conor.dooley@microchip.com>
To: <i.bornyakov@metrotek.ru>
Cc: <Conor.Dooley@microchip.com>, <corbet@lwn.net>,
<devicetree@vger.kernel.org>, <hao.wu@intel.com>,
<krzysztof.kozlowski+dt@linaro.org>, <linux-doc@vger.kernel.org>,
<linux-fpga@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<mdf@kernel.org>, <robh+dt@kernel.org>, <system@metrotek.ru>,
<trix@redhat.com>, <yilun.xu@intel.com>,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v20 0/4] Microchip Polarfire FPGA manager
Date: Mon, 20 Jun 2022 11:57:48 +0100 [thread overview]
Message-ID: <20220620105747.2145347-1-conor.dooley@microchip.com> (raw)
In-Reply-To: <20220620100745.yxjmq2qtsicxlrgn@h-e2.ddg>
I had a quick check in -next and there's an entry for the BMC
driver there.
How about the following? I put you as R, but clearly if you want to be
maintainer then you are *more than* qualified.
Feel free to edit the patch if so, either is fine by me.
You can tack this onto a v21 if you have more changes or I can resend
standalone once the driver is merged.
Thanks,
Conor.
From: Conor Dooley <conor.dooley@microchip.com>
Date: Mon, 20 Jun 2022 11:46:19 +0100
Subject: [PATCH] MAINTAINERS: add polarfire fpga programmer drivers
Add a MAINTAINERS entry for the newly added PolarFire (MPF) SPI slave
programming driver.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
MAINTAINERS | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 168e0af869a7..60ab3c4bf65d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7869,6 +7869,14 @@ S: Maintained
F: Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
F: drivers/fpga/intel-m10-bmc-sec-update.c
+FPGA PolarFire Drivers
+M: Conor Dooley <conor.dooley@microchip.com>
+R: Ivan Bornyakov <i.bornyakov@metrotek.ru>
+L: linux-fpga@vger.kernel.org
+S: Supported
+F: Documentation/devicetree/bindings/fpga/microchip,mpf-spi-fpga-mgr.yaml
+F: drivers/fpga/microchip-spi.c
+
FPU EMULATOR
M: Bill Metzenthen <billm@melbpc.org.au>
S: Maintained
base-commit: 07dc787be2316e243a16a33d0a9b734cd9365bd3
--
2.36.1
next prev parent reply other threads:[~2022-06-20 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 13:48 [PATCH v20 0/4] Microchip Polarfire FPGA manager Ivan Bornyakov
2022-06-17 13:48 ` [PATCH v20 1/4] fpga: fpga-mgr: support bitstream offset in image buffer Ivan Bornyakov
2022-06-21 10:27 ` Xu Yilun
2022-06-17 13:48 ` [PATCH v20 2/4] docs: fpga: mgr: document parse_header() callback Ivan Bornyakov
2022-06-21 10:36 ` Xu Yilun
2022-06-17 13:48 ` [PATCH v20 3/4] fpga: microchip-spi: add Microchip MPF FPGA manager Ivan Bornyakov
2022-06-17 13:48 ` [PATCH v20 4/4] dt-bindings: fpga: add binding doc for microchip-spi fpga mgr Ivan Bornyakov
2022-06-19 18:39 ` [PATCH v20 0/4] Microchip Polarfire FPGA manager Conor.Dooley
2022-06-20 10:07 ` Ivan Bornyakov
2022-06-20 10:57 ` Conor Dooley [this message]
2022-06-20 11:01 ` Conor.Dooley
2022-06-20 18:01 ` Ivan Bornyakov
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=20220620105747.2145347-1-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=hao.wu@intel.com \
--cc=i.bornyakov@metrotek.ru \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=robh+dt@kernel.org \
--cc=system@metrotek.ru \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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).