From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yi xin Zhu <yzhu@maxlinear.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>
Cc: Jack Ping Chng <jchng@maxlinear.com>,
Suresh Nagaraj <sureshnagaraj@maxlinear.com>
Subject: Re: [PATCH 1/5] dmaengine: lgm-dma: Move platfrom data to device tree
Date: Wed, 30 Jul 2025 10:54:03 +0200 [thread overview]
Message-ID: <fd17b4a9-119d-47a3-8fef-5f89a30cb212@kernel.org> (raw)
In-Reply-To: <SA1PR19MB490993CCD0F80D63501DAE92C224A@SA1PR19MB4909.namprd19.prod.outlook.com>
On 30/07/2025 10:43, Yi xin Zhu wrote:
>>
>>
>>
>> Best regards,
>> Krzysztof
>
> I'll include detailed comments to explain why the compatible change is required.
It is unlikely you will come with good arguments for breaking ABI.
Anyway, if you keep going that way, explain in terms of ABI impact.
See also ABI docs, writing bindings and submitting patches.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-30 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 2:45 [PATCH 1/5] dmaengine: lgm-dma: Move platfrom data to device tree Zhu Yixin
2025-07-30 2:45 ` [PATCH 2/5] dmaengine: lgm-dma: Correct ORRC MAX counter value Zhu Yixin
2025-07-30 2:45 ` [PATCH 3/5] dmaengine: lgm-dma: split legacy DMA and HDMA functions Zhu Yixin
2025-07-30 6:20 ` Krzysztof Kozlowski
2025-07-30 8:52 ` Yi xin Zhu
2025-07-30 2:45 ` [PATCH 4/5] dmaengine: lgm-dma: Added HDMA software mode TX function Zhu Yixin
2025-07-30 6:21 ` Krzysztof Kozlowski
2025-07-30 8:59 ` Yi xin Zhu
2025-07-30 16:17 ` kernel test robot
2025-07-30 2:45 ` [PATCH 5/5] dmaengine: lgm_dma: Added HDMA RX interrupt handle functions Zhu Yixin
2025-07-30 6:19 ` [PATCH 1/5] dmaengine: lgm-dma: Move platfrom data to device tree Krzysztof Kozlowski
2025-07-30 8:43 ` Yi xin Zhu
2025-07-30 8:54 ` Krzysztof Kozlowski [this message]
2025-07-31 5:44 ` Yi xin Zhu
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=fd17b4a9-119d-47a3-8fef-5f89a30cb212@kernel.org \
--to=krzk@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jchng@maxlinear.com \
--cc=sureshnagaraj@maxlinear.com \
--cc=vkoul@kernel.org \
--cc=yzhu@maxlinear.com \
/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