From: "Rob Herring (Arm)" <robh@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH v2 1/1] PCI: dwc: Remove not-going-to-be-supported code for Baikal SoC
Date: Mon, 23 Feb 2026 12:58:24 -0600 [thread overview]
Message-ID: <177187310274.163191.14167430732235845058.robh@kernel.org> (raw)
In-Reply-To: <20260220142600.2397070-1-andriy.shevchenko@linux.intel.com>
On Fri, 20 Feb 2026 15:21:12 +0100, Andy Shevchenko wrote:
> As noticed in the discussion [1] the Baikal SoC and platforms
> are not going to be finalized, hence remove stale code.
>
> Link: https://lore.kernel.org/lkml/22b92ddf-6321-41b5-8073-f9c7064d3432@infradead.org/ [1]
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>
> v2: removed YAML file
>
> .../bindings/pci/baikal,bt1-pcie.yaml | 168 -----
> drivers/pci/controller/dwc/Kconfig | 9 -
> drivers/pci/controller/dwc/Makefile | 1 -
> drivers/pci/controller/dwc/pcie-bt1.c | 645 ------------------
> 4 files changed, 823 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/pci/baikal,bt1-pcie.yaml
> delete mode 100644 drivers/pci/controller/dwc/pcie-bt1.c
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-02-23 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 14:21 [PATCH v2 1/1] PCI: dwc: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-23 18:58 ` Rob Herring (Arm) [this message]
2026-03-02 13:33 ` Andy Shevchenko
2026-03-02 13:51 ` Manivannan Sadhasivam
2026-03-02 13:57 ` Andy Shevchenko
2026-03-02 14:07 ` Manivannan Sadhasivam
2026-03-02 14:16 ` Andy Shevchenko
2026-03-02 14:12 ` Manivannan Sadhasivam
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=177187310274.163191.14167430732235845058.robh@kernel.org \
--to=robh@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=p.zabel@pengutronix.de \
/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.