From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhu Yixin <yzhu@maxlinear.com>,
dmaengine@vger.kernel.org, vkoul@kernel.org
Cc: jchng@maxlinear.com, sureshnagaraj@maxlinear.com
Subject: Re: [PATCH 3/5] dmaengine: lgm-dma: split legacy DMA and HDMA functions
Date: Wed, 30 Jul 2025 08:20:33 +0200 [thread overview]
Message-ID: <e3462ab4-73fe-4960-af4c-a7360288e3e3@kernel.org> (raw)
In-Reply-To: <20250730024547.3160871-3-yzhu@maxlinear.com>
On 30/07/2025 04:45, Zhu Yixin wrote:
> Move legacy DMA functions into lgm-cdma.c.
> Move HDMA functions into lgm-hdma.c
> Keep the driver flow and general functions in lgm-dma.c
>
> Signed-off-by: Zhu Yixin <yzhu@maxlinear.com>
> ---
> .../devicetree/bindings/dma/intel,ldma.yaml | 7 +-
> drivers/dma/lgm/Makefile | 2 +-
> drivers/dma/lgm/lgm-cdma.c | 492 ++++++++++
> drivers/dma/lgm/lgm-dma.c | 839 ++----------------
> drivers/dma/lgm/lgm-dma.h | 278 ++++++
> drivers/dma/lgm/lgm-hdma.c | 130 +++
> 6 files changed, 961 insertions(+), 787 deletions(-)
> create mode 100644 drivers/dma/lgm/lgm-cdma.c
> create mode 100644 drivers/dma/lgm/lgm-dma.h
> create mode 100644 drivers/dma/lgm/lgm-hdma.c
>
> diff --git a/Documentation/devicetree/bindings/dma/intel,ldma.yaml b/Documentation/devicetree/bindings/dma/intel,ldma.yaml
> index 59f928297613..f91d849edc4c 100644
> --- a/Documentation/devicetree/bindings/dma/intel,ldma.yaml
> +++ b/Documentation/devicetree/bindings/dma/intel,ldma.yaml
> @@ -15,7 +15,8 @@ allOf:
> properties:
> compatible:
> enum:
> - - intel,lgm-ldma
> + - intel,lgm-cdma
> + - intel,lgm-hdma
NAK, stop random changes to compatibles.
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-30 6:20 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 [this message]
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
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=e3462ab4-73fe-4960-af4c-a7360288e3e3@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