[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+rnUB2pDjf6qFF7ThtSD-C8MMZUrhJmTYKfts34Zhr-A@mail.gmail.com>
Date: Thu, 15 Aug 2024 15:15:52 -0600
From: Rob Herring <robh@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: Frank Li <Frank.Li@....com>, Bjorn Helgaas <bhelgaas@...gle.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, Krzysztof Wilczyński <kw@...ux.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Zhiqiang.Hou@....com,
linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH 4/4] MAINTAINERS: drop NXP LAYERSCAPE GEN4 CONTROLLER
On Thu, Aug 15, 2024 at 9:53 AM Manivannan Sadhasivam
<manivannan.sadhasivam@...aro.org> wrote:
>
> 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.
Is anyone really going to pay attention to that? It doesn't sound like
there's anyone to really care, and it is the company that made the h/w
asking to remove it. The only thing people use pre-production h/w for
once there's production h/w is as a dust collector.
If anyone complains, it's simple enough to revert these patches.
Rob
Powered by blists - more mailing lists