From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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: Wed, 25 Feb 2026 10:45:22 +0100 [thread overview]
Message-ID: <f2636d0d-9568-4a15-b17f-8e3b7b8d108f@kernel.org> (raw)
In-Reply-To: <aZ7DYTKrALZQKIy_@smile.fi.intel.com>
On 25/02/2026 10:39, Andy Shevchenko wrote:
>>>> Separate patch in these patch series! The ABI documentation ALWAYS goes
>>>> with the implementation. Every patch on LKML follows that rule and also
>>>> it is explicitly documented in DT submitting patches.
>>>
>>> I see, it seems too hard to do this right from the start.
>>
>> Just like reverts of multiple commits are going in reversed order of
>> commits, then this is done in exact reverse order, so you can simply
>> look at any other patchset and do the reverse. Just took the latets from:
>> https://lore.kernel.org/linux-devicetree/
>>
>> So this is adding:
>> https://lore.kernel.org/linux-devicetree/20260225-ina4230-v1-0-92b1de981d46@flipper.net/T/#m7817a527e6819c9383456aeaa0fe22f86e470d6f
>>
>> and removing would be exact revert, reverse order, with of course
>> appropriate subjects and commit msgs.
>
> These can't be done as pure set of reverts. This needs a manual work.
I understand, I wanted to explain how to deduce the proper flow.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-25 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 15:05 Andy Shevchenko
2026-02-24 15:18 ` Krzysztof Kozlowski
2026-02-24 15:24 ` Andy Shevchenko
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 [this message]
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=f2636d0d-9568-4a15-b17f-8e3b7b8d108f@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--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 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®