public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: linux-kernel@vger.kernel.org, monstr@monstr.eu,
	michal.simek@xilinx.com, git@xilinx.com
Cc: Conor Dooley <conor+dt@kernel.org>,
	Krishna Potthuri <sai.krishna.potthuri@amd.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: xilinx: Remove Rajan, Jolly and Manish
Date: Mon, 5 Jun 2023 13:17:50 +0200	[thread overview]
Message-ID: <54ee38d1-5924-8305-0da8-0a2d35ff80a7@monstr.eu> (raw)
In-Reply-To: <9b252dd71c82593fa6b137eca2174d9ab6e57f7a.1684828606.git.michal.simek@amd.com>



On 5/23/23 09:56, Michal Simek wrote:
> Rajan, Jolly and Manish are no longer work for AMD/Xilinx and there is no
> activity from them to continue to maintain bindings that's why remove them.
> 
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
> 
>   Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml    | 2 --
>   .../bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml        | 1 -
>   .../bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml         | 1 -
>   .../devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml        | 1 -
>   4 files changed, 5 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml b/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml
> index 93ae349cf9e9..5cbb34d0b61b 100644
> --- a/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml
> +++ b/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml
> @@ -8,8 +8,6 @@ title: Xilinx Versal clock controller
>   
>   maintainers:
>     - Michal Simek <michal.simek@amd.com>
> -  - Jolly Shah <jolly.shah@xilinx.com>
> -  - Rajan Vaja <rajan.vaja@xilinx.com>
>   
>   description: |
>     The clock controller is a hardware block of Xilinx versal clock tree. It
> diff --git a/Documentation/devicetree/bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml b/Documentation/devicetree/bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml
> index 6b62d5d83476..87ff9ee098f5 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/snps,dw-umctl2-ddrc.yaml
> @@ -8,7 +8,6 @@ title: Synopsys DesignWare Universal Multi-Protocol Memory Controller
>   
>   maintainers:
>     - Krzysztof Kozlowski <krzk@kernel.org>
> -  - Manish Narani <manish.narani@xilinx.com>
>     - Michal Simek <michal.simek@amd.com>
>   
>   description: |
> diff --git a/Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml b/Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml
> index 7864a1c994eb..75143db51411 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/xlnx,zynq-ddrc-a05.yaml
> @@ -8,7 +8,6 @@ title: Zynq A05 DDR Memory Controller
>   
>   maintainers:
>     - Krzysztof Kozlowski <krzk@kernel.org>
> -  - Manish Narani <manish.narani@xilinx.com>
>     - Michal Simek <michal.simek@amd.com>
>   
>   description:
> diff --git a/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> index cdebfa991e06..24ad0614e61b 100644
> --- a/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/xlnx,zynqmp-pinctrl.yaml
> @@ -8,7 +8,6 @@ title: Xilinx ZynqMP Pinctrl
>   
>   maintainers:
>     - Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
> -  - Rajan Vaja <rajan.vaja@xilinx.com>
>   
>   description: |
>     Please refer to pinctrl-bindings.txt in this directory for details of the

Applied.
M

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs
TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2023-06-05 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23  7:56 [PATCH] dt-bindings: xilinx: Remove Rajan, Jolly and Manish Michal Simek
2023-05-23 17:03 ` Conor Dooley
2023-06-05 11:17 ` Michal Simek [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=54ee38d1-5924-8305-0da8-0a2d35ff80a7@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@xilinx.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sai.krishna.potthuri@amd.com \
    --cc=sboyd@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