From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
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>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v1 1/1] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC
Date: Tue, 24 Feb 2026 13:05:24 +0100 [thread overview]
Message-ID: <2bf95220-aaa7-48dc-a3f5-c5fd43c6ae67@kernel.org> (raw)
In-Reply-To: <20260224115830.3501050-1-andriy.shevchenko@linux.intel.com>
On 24/02/2026 12:58, 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>
> ---
> .../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
>
You got the feedback from Rob, so please implement it in all new patches
PAST that feedback. No need to resend old ones, but if you are making
new work - respect that feedback.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-24 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 11:58 [PATCH v1 1/1] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-24 12:05 ` Krzysztof Kozlowski [this message]
2026-02-24 13:43 ` Andy Shevchenko
2026-02-24 18:53 ` Randy Dunlap
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=2bf95220-aaa7-48dc-a3f5-c5fd43c6ae67@kernel.org \
--to=krzk@kernel.org \
--cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox