From: Randy Dunlap <rdunlap@infradead.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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>
Subject: Re: [PATCH v1 2/2] dt-bindings: bus: Remove unused bindings
Date: Thu, 26 Feb 2026 23:37:13 -0800 [thread overview]
Message-ID: <03dc4eb0-9064-4beb-85d0-3679918e10d6@infradead.org> (raw)
In-Reply-To: <20260227072726.1142944-3-andriy.shevchenko@linux.intel.com>
On 2/26/26 11:26 PM, Andy Shevchenko wrote:
> As stated in [1] the Baikal platforms are not supported and
> the respective driver code has just been removed. Remove
> unused bindings.
>
> Link: https://lore.kernel.org/lkml/22b92ddf-6321-41b5-8073-f9c7064d3432@infradead.org/ [1]
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> .../bindings/bus/baikal,bt1-apb.yaml | 90 ---------------
> .../bindings/bus/baikal,bt1-axi.yaml | 107 ------------------
> 2 files changed, 197 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-apb.yaml
> delete mode 100644 Documentation/devicetree/bindings/bus/baikal,bt1-axi.yaml
>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
--
~Randy
next prev parent reply other threads:[~2026-02-27 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 7:26 [PATCH v1 0/2] bus: Remove Baikal SoC pieces Andy Shevchenko
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 [this message]
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=03dc4eb0-9064-4beb-85d0-3679918e10d6@infradead.org \
--to=rdunlap@infradead.org \
--cc=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=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
all inboxes | Powered by JetHome®