From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 1/1] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC
Date: Tue, 24 Feb 2026 17:24:34 +0200 [thread overview]
Message-ID: <aZ3CstVndYOUWPz1@smile.fi.intel.com> (raw)
In-Reply-To: <0eceef2b-4d33-4a09-af92-6b4131a1d8c2@kernel.org>
On Tue, Feb 24, 2026 at 04:18:36PM +0100, Krzysztof Kozlowski wrote:
> On 24/02/2026 16:05, 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: dropped DT bindings change (Krzysztof)
> >
>
> I think we misunderstood each other. I was speaking about that feedback:
> https://lore.kernel.org/linux-devicetree/20260223185754.GA151596-robh@kernel.org/
>
> so bindings are separate patches.
>
> Was there any other feedback?
Now you are totally confused me.
I did what you asked, I split bindings removal to a separate patch. The code is
also removed in this patch. What do you want?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-02-24 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 15:05 [PATCH v2 1/1] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-24 15:18 ` Krzysztof Kozlowski
2026-02-24 15:24 ` Andy Shevchenko [this message]
2026-02-24 15:29 ` Andy Shevchenko
2026-02-25 8:02 ` Krzysztof Kozlowski
2026-02-25 9:23 ` Andy Shevchenko
2026-02-25 9:33 ` Krzysztof Kozlowski
2026-02-25 9:39 ` Andy Shevchenko
2026-02-25 9:45 ` Krzysztof Kozlowski
2026-02-25 10:09 ` Andy Shevchenko
2026-02-24 18:55 ` 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=aZ3CstVndYOUWPz1@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.