From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Randy Dunlap <rdunlap@infradead.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 0/2] bus: Remove Baikal SoC pieces
Date: Fri, 27 Feb 2026 08:26:24 +0100 [thread overview]
Message-ID: <20260227072726.1142944-1-andriy.shevchenko@linux.intel.com> (raw)
Baikal SoC and platform support won't be finalised, remove stale pieces.
Andy Shevchenko (2):
bus: Remove not-going-to-be-supported code for Baikal SoC
dt-bindings: bus: Remove unused bindings
.../bindings/bus/baikal,bt1-apb.yaml | 90 ----
.../bindings/bus/baikal,bt1-axi.yaml | 107 -----
drivers/bus/Kconfig | 30 --
drivers/bus/Makefile | 2 -
drivers/bus/bt1-apb.c | 396 ------------------
drivers/bus/bt1-axi.c | 292 -------------
6 files changed, 917 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-apb.yaml
delete mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-axi.yaml
delete mode 100644 drivers/bus/bt1-apb.c
delete mode 100644 drivers/bus/bt1-axi.c
--
2.50.1
next reply other threads:[~2026-02-27 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 7:26 Andy Shevchenko [this message]
2026-02-27 7:26 ` [PATCH v1 1/2] bus: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-27 7:37 ` Randy Dunlap
2026-02-27 7:26 ` [PATCH v1 2/2] dt-bindings: bus: Remove unused bindings Andy Shevchenko
2026-02-27 7:37 ` Randy Dunlap
2026-03-11 22:43 ` [PATCH v1 0/2] bus: Remove Baikal SoC pieces Rob Herring
2026-03-12 9:23 ` Andy Shevchenko
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=20260227072726.1142944-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rdunlap@infradead.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.