mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Kees Cook <kees@kernel.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: linux-amlogic@lists.infradead.org, dmaengine@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: dma: Add Amlogic general DMA
Date: Fri, 19 Dec 2025 09:58:58 +0800	[thread overview]
Message-ID: <44150c9e-9a0d-411f-8532-ab03a632bfbf@amlogic.com> (raw)
In-Reply-To: <83c771e7-f32b-48e4-91ab-d7c3b9746e14@kernel.org>

Hi Krzysztof,
    Thanks for your reply.

On 2025/12/16 16:45, Krzysztof Kozlowski wrote:
> I don't know what you mean by "general" but it feels like wildcard, not
> SoC, so that would be a no-go. Read writing bindings or several talks
> about this.

I will named it using the name of SoC in V2.

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2025-12-19  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  8:03 [PATCH 0/3] " Xianwei Zhao via B4 Relay
2025-12-16  8:03 ` [PATCH 1/3] dt-bindings: dma: " Xianwei Zhao via B4 Relay
2025-12-16  8:45   ` Krzysztof Kozlowski
2025-12-19  1:58     ` Xianwei Zhao [this message]
2025-12-16  8:03 ` [PATCH 2/3] dma: amlogic: Add general DMA driver for SoCs Xianwei Zhao via B4 Relay
2025-12-16  8:46   ` Krzysztof Kozlowski
2025-12-19  2:04     ` Xianwei Zhao
2025-12-16  9:09   ` neil.armstrong
2025-12-19  2:35     ` Xianwei Zhao
2025-12-20 18:21   ` kernel test robot
2025-12-16  8:03 ` [PATCH 3/3] MAINTAINERS: Add an entry for Amlogic DMA driver Xianwei Zhao via B4 Relay

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=44150c9e-9a0d-411f-8532-ab03a632bfbf@amlogic.com \
    --to=xianwei.zhao@amlogic.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=gustavoars@kernel.org \
    --cc=kees@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@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