From: Dinh Nguyen <dinguyen@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Khairul Anuar Romli <khairul.anuar.romli@altera.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
Vinod Koul <vkoul@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Niravkumar L Rabara <niravkumar.l.rabara@intel.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 0/3] Add dma-coherent property
Date: Wed, 17 Dec 2025 04:45:35 -0600 [thread overview]
Message-ID: <6475226a-0291-485b-af93-054ed3cfe664@kernel.org> (raw)
In-Reply-To: <871pktscld.fsf@bootlin.com>
On 12/17/25 03:05, Miquel Raynal wrote:
> Hello Dinh,
>
>>>> Applied!
>>> Have you applied all 3 patches? If yes, where? It happened during the
>>> merge window but I see nothing in v6.19-rc1. I was about to take the mtd
>>> binding patch, but if you took it already that's fine, I'll mark this
>>> series as already applied.
>>>
>>
>> Yes, I took all 3 and staging it in my tree for v6.20.
>
> Noted. If you happen to rebase your own tree you can add my
>
> Acked-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
I'll do that.
Thanks,
Dinh
prev parent reply other threads:[~2025-12-17 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 23:47 Khairul Anuar Romli
2025-12-02 23:47 ` [PATCH v2 1/3] dt-bindings: mtd: cdns,hp-nfc: " Khairul Anuar Romli
2025-12-04 21:36 ` Rob Herring (Arm)
2025-12-02 23:47 ` [PATCH v2 2/3] dt-bindings: dma: snps,dw-axi-dmac: add " Khairul Anuar Romli
2025-12-04 21:36 ` Rob Herring (Arm)
2025-12-02 23:47 ` [PATCH v2 3/3] arm64: dts: socfpga: agilex5: Add " Khairul Anuar Romli
2025-12-09 2:31 ` [PATCH v2 0/3] " Dinh Nguyen
2025-12-16 8:12 ` Miquel Raynal
2025-12-17 3:22 ` Dinh Nguyen
2025-12-17 9:05 ` Miquel Raynal
2025-12-17 10:45 ` Dinh Nguyen [this message]
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=6475226a-0291-485b-af93-054ed3cfe664@kernel.org \
--to=dinguyen@kernel.org \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=khairul.anuar.romli@altera.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=niravkumar.l.rabara@intel.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--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
Powered by JetHome