From: Marek Vasut <marex@nabladev.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Aswath Govindraju <a-govindraju@ti.com>,
Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>, Frank Li <Frank.Li@nxp.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563
Date: Thu, 12 Nov 2026 18:13:53 +0100 [thread overview]
Message-ID: <d218212f-191c-47cc-843a-d4587e478fc0@nabladev.com> (raw)
In-Reply-To: <avXqWxBQBK2lKPMv@parshuram>
On 11/12/26 5:33 PM, Vinod Koul wrote:
> On 10-11-26, 14:59, Marek Vasut wrote:
>> On 10/28/26 7:59 AM, Vinod Koul wrote:
>
>>>> +CC Vinod, is this patch OK with you ?
>>>
>>> Looks good to me, I will pick this after rc1 (monday)
>> I would like to do a brief reminder here, so this won't get lost, since rc1
>> is now out and I don't see this in dmaengine.git.
>
> I have picked it up in phy tree...
Thank you !
next prev parent reply other threads:[~2026-11-13 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:46 [PATCH v6 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563 Marek Vasut
2026-09-30 21:46 ` [PATCH v6 2/3] dt-bindings: arm: fsl: Document Data Modul i.MX95 eDM SBC Marek Vasut
2026-09-30 21:46 ` [PATCH v6 3/3] arm64: dts: imx95: Add support for " Marek Vasut
2026-10-27 17:18 ` [PATCH v6 1/3] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6563 Marek Vasut
2026-10-28 6:59 ` Vinod Koul
2026-11-10 13:59 ` Marek Vasut
2026-11-12 16:33 ` Vinod Koul
2026-11-12 17:13 ` Marek Vasut [this message]
2026-11-12 9:03 ` (subset) " Vinod Koul
2026-11-12 12:35 ` Marek Vasut
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=d218212f-191c-47cc-843a-d4587e478fc0@nabladev.com \
--to=marex@nabladev.com \
--cc=Frank.Li@nxp.com \
--cc=a-govindraju@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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