From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
Zhiqiang.Hou@nxp.com, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH 4/4] MAINTAINERS: drop NXP LAYERSCAPE GEN4 CONTROLLER
Date: Thu, 15 Aug 2024 21:23:43 +0530 [thread overview]
Message-ID: <20240815155343.GC2562@thinkpad> (raw)
In-Reply-To: <20240808-mobivel_cleanup-v1-4-f4f6ea5b16de@nxp.com>
On Thu, Aug 08, 2024 at 12:02:17PM -0400, Frank Li wrote:
> LX2160 Rev1 use mobivel PCIe controller, but Rev2 switch to designware
> PCIe controller. Rev2 is mass production chip. Rev1 will not be maintained
> so drop maintainer information for that.
>
Instead of suddenly removing the code and breaking users, you can just mark the
driver as 'Obsolete' in MAINTAINERS. Then after some point of time, we could
hopefully remove.
- Mani
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> MAINTAINERS | 8 --------
> 1 file changed, 8 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1e71f97fb6749..9b683899cd088 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17556,14 +17556,6 @@ S: Supported
> F: Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
> F: drivers/pci/controller/pci-tegra.c
>
> -PCI DRIVER FOR NXP LAYERSCAPE GEN4 CONTROLLER
> -M: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> -L: linux-pci@vger.kernel.org
> -L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> -S: Maintained
> -F: Documentation/devicetree/bindings/pci/layerscape-pcie-gen4.txt
> -F: drivers/pci/controller/mobiveil/pcie-layerscape-gen4.c
> -
> PCI DRIVER FOR PLDA PCIE IP
> M: Daire McNamara <daire.mcnamara@microchip.com>
> L: linux-pci@vger.kernel.org
>
> --
> 2.34.1
>
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-08-15 15:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 16:02 [PATCH 0/4] PCI: mobivel: Drop layerscape gen4 support Frank Li
2024-08-08 16:02 ` [PATCH 1/4] dt-bindings: PCI: layerscape-pci: drop compatible string fsl,lx2160a-pcie Frank Li
2024-08-10 14:58 ` Krzysztof Kozlowski
2024-08-08 16:02 ` [PATCH 2/4] dt-bindings: PCI: drop layerscape-pcie-gen4.txt Frank Li
2024-08-10 15:00 ` Krzysztof Kozlowski
2024-08-08 16:02 ` [PATCH 3/4] PCI: mobiveil: Drop layerscape-gen4 support Frank Li
2024-08-08 17:26 ` Bjorn Helgaas
2024-08-08 18:08 ` Frank Li
2024-08-10 15:01 ` Krzysztof Kozlowski
2024-08-08 16:02 ` [PATCH 4/4] MAINTAINERS: drop NXP LAYERSCAPE GEN4 CONTROLLER Frank Li
2024-08-10 14:54 ` Krzysztof Kozlowski
2024-08-15 15:53 ` Manivannan Sadhasivam [this message]
2024-08-15 21:15 ` Rob Herring
2024-08-16 5:42 ` Manivannan Sadhasivam
2024-08-16 17:09 ` Frank Li
2024-08-16 18:15 ` Bjorn Helgaas
2024-08-16 19:17 ` Frank Li
2024-08-16 23:14 ` Olof Johansson
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=20240815155343.GC2562@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=Frank.Li@nxp.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.