linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dragan Cvetic <dragan.cvetic@xilinx.com>,
	arnd@arndb.de, gregkh@linuxfoundation.org,
	michal.simek@xilinx.com, linux-arm-kernel@lists.infradead.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Derek Kiernan <derek.kiernan@xilinx.com>
Subject: Re: [PATCH V5 11/11] MAINTAINERS: add maintainer for SD-FEC
Date: Mon, 10 Jun 2019 11:59:48 -0700	[thread overview]
Message-ID: <4491ae98b10f4519874141eb39cd2f0b5491b3a5.camel@perches.com> (raw)
In-Reply-To: <1560038656-380620-12-git-send-email-dragan.cvetic@xilinx.com>

On Sun, 2019-06-09 at 01:04 +0100, Dragan Cvetic wrote:
> Add maintainer entry for Xilinx SD-FEC driver support.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -17345,6 +17345,17 @@ S:	Supported
>  F:	Documentation/filesystems/xfs.txt
>  F:	fs/xfs/
>  
> +XILINX SD-FEC IP CORES
> +M:	Derek Kiernan <derek.kiernan@xilinx.com>
> +M:	Dragan Cvetic <dragan.cvetic@xilinx.com>
> +S:	Maintained
> +F:	Documentation/devicetree/bindings/misc/xlnx,sd-fec.txt
> +F:	Documentation/misc-devices/xilinx_sdfec.rst
> +F:	drivers/misc/xilinx_sdfec.c
> +F:	drivers/misc/Kconfig
> +F:	drivers/misc/Makefile

I suggest that you do not want to be nor are responsible
for the Kconfig and Makefile just because entries in
those files are associated to xilinx files.




      reply	other threads:[~2019-06-10 18:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  0:04 [PATCH V5 00/12] misc: xilinx sd-fec drive Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 01/11] dt-bindings: xilinx-sdfec: Add SDFEC binding Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 02/11] misc: xilinx-sdfec: add core driver Dragan Cvetic
2019-06-09 11:22   ` Greg KH
2019-06-09 18:48     ` Dragan Cvetic
2019-06-09 21:10       ` Greg KH
2019-06-09  0:04 ` [PATCH V5 03/11] misc: xilinx_sdfec: Add CCF support Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 04/11] misc: xilinx_sdfec: Store driver config and state Dragan Cvetic
2019-06-09 11:27   ` Greg KH
2019-06-09 19:04     ` Dragan Cvetic
2019-06-09 21:11       ` Greg KH
2019-06-09  0:04 ` [PATCH V5 05/11] misc: xilinx_sdfec: Add ability to configure turbo Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 06/11] misc: xilinx_sdfec: Add ability to configure LDPC Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 07/11] misc: xilinx_sdfec: Add ability to get/set config Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 08/11] misc: xilinx_sdfec: Support poll file operation Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 09/11] misc: xilinx_sdfec: Add stats & status ioctls Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 10/11] Docs: misc: xilinx_sdfec: Add documentation Dragan Cvetic
2019-06-09  0:04 ` [PATCH V5 11/11] MAINTAINERS: add maintainer for SD-FEC Dragan Cvetic
2019-06-10 18:59   ` Joe Perches [this message]

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=4491ae98b10f4519874141eb39cd2f0b5491b3a5.camel@perches.com \
    --to=joe@perches.com \
    --cc=arnd@arndb.de \
    --cc=derek.kiernan@xilinx.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=robh+dt@kernel.org \
    /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).