The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <i.bornyakov@metrotek.ru>, <mdf@kernel.org>, <hao.wu@intel.com>,
	<yilun.xu@intel.com>, <trix@redhat.com>, <corbet@lwn.net>
Cc: <Conor.Dooley@microchip.com>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <linux-fpga@vger.kernel.org>,
	<linux-doc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <system@metrotek.ru>
Subject: Re: [PATCH v21 5/5] MAINTAINERS: add Microchip PolarFire FPGA drivers entry
Date: Tue, 21 Jun 2022 15:48:45 +0000	[thread overview]
Message-ID: <78f97ca4-f124-ae5d-a46a-ec0a1f3c0fe7@microchip.com> (raw)
In-Reply-To: <20220621153847.103052-6-i.bornyakov@metrotek.ru>



On 21/06/2022 16:38, Ivan Bornyakov wrote:
> Add MAINTAINERS entry for the newly added Microchip PolarFire (MPF) FPGA
> manager. Add myself as a reviewer and Conor Dooley as a maintainer.
> 
> Suggested-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Ivan Bornyakov <i.bornyakov@metrotek.ru>
> ---
>  MAINTAINERS | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b774f21828f7..ed2517574804 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7884,6 +7884,14 @@ S:	Maintained
>  F:	Documentation/ABI/testing/sysfs-driver-intel-m10-bmc-sec-update
>  F:	drivers/fpga/intel-m10-bmc-sec-update.c
>  
> +MICROCHIP POLARFIRE FPGA 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

Acked-by: Conor Dooley <conor.dooley@microchip.com>

  reply	other threads:[~2022-06-21 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 15:38 [PATCH v21 0/5] Microchip Polarfire FPGA manager Ivan Bornyakov
2022-06-21 15:38 ` [PATCH v21 1/5] fpga: fpga-mgr: support bitstream offset in image buffer Ivan Bornyakov
2022-06-23  9:28   ` Xu Yilun
2022-06-21 15:38 ` [PATCH v21 2/5] docs: fpga: mgr: document parse_header() callback Ivan Bornyakov
2022-06-21 15:38 ` [PATCH v21 3/5] fpga: microchip-spi: add Microchip MPF FPGA manager Ivan Bornyakov
2022-06-23  9:29   ` Xu Yilun
2022-06-23  9:48     ` Ivan Bornyakov
2022-06-23  9:50       ` Xu Yilun
2022-06-21 15:38 ` [PATCH v21 4/5] dt-bindings: fpga: add binding doc for microchip-spi fpga mgr Ivan Bornyakov
2022-06-21 15:38 ` [PATCH v21 5/5] MAINTAINERS: add Microchip PolarFire FPGA drivers entry Ivan Bornyakov
2022-06-21 15:48   ` Conor.Dooley [this message]
2022-06-23  9:32   ` Xu Yilun

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=78f97ca4-f124-ae5d-a46a-ec0a1f3c0fe7@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