From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Conor Dooley <conor@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3 0/2] memory: Drop Baikal SoC code and bindings
Date: Wed, 25 Feb 2026 18:37:19 +0100 [thread overview]
Message-ID: <20260225173930.3819351-1-andriy.shevchenko@linux.intel.com> (raw)
The platform is not going to be supported, remove stale code and bindings.
In v3:
- combined patches in a series (Krzysztof)
- collected tags
In v2:
- split bindings removal to a separate patch (Krzysztof)
Andy Shevchenko (2):
memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal
SoC
dt-bindings: cache: bt1-l2-ctl: Remove unused bindings
.../bindings/cache/baikal,bt1-l2-ctl.yaml | 63 ----
drivers/memory/Kconfig | 11 -
drivers/memory/Makefile | 1 -
drivers/memory/bt1-l2-ctl.c | 323 ------------------
4 files changed, 398 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
delete mode 100644 drivers/memory/bt1-l2-ctl.c
--
2.50.1
next reply other threads:[~2026-02-25 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 17:37 Andy Shevchenko [this message]
2026-02-25 17:37 ` [PATCH v3 1/2] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-25 17:37 ` [PATCH v3 2/2] dt-bindings: cache: bt1-l2-ctl: Remove unused bindings Andy Shevchenko
2026-02-26 7:30 ` [PATCH v3 0/2] memory: Drop Baikal SoC code and bindings Krzysztof Kozlowski
2026-02-26 7:44 ` 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=20260225173930.3819351-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox