From: patchwork-bot+netdevbpf@kernel.org
To: Vincent Jardin <vjardin@free.fr>
Cc: ivecera@redhat.com, Prathosh.Satish@microchip.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
vadim.fedorenko@linux.dev, arkadiusz.kubalewski@intel.com,
jiri@resnulli.us, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dpll: zl3073x: add Microchip ZL30643 support
Date: Thu, 06 Aug 2026 02:10:14 +0000 [thread overview]
Message-ID: <178598221489.607412.12370158005617212276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260730-for-upstream-zl30643-v2-0-0ea0bbd03755@free.fr>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 30 Jul 2026 19:35:34 +0200 you wrote:
> The Microchip ZL30643 (chip ID 0x0E3B) is a 3 DPLL channel member of
> the ZL3064x timing family, register compatible with the
> ZL30733 of the ZL3073x family.
>
> Patch 1 describes it in the binding as a fallback to the register-
> equivalent microchip,zl30733.
> Patch 2 adds the 0x0E3B runtime chip-ID table entry; no new match
> strings, the fallback binds via the existing microchip,zl30733
> entry.
>
> [...]
Here is the summary with links:
- [v2,1/2] dt-bindings: dpll: zl3073x: ZL30643 is compatible
https://git.kernel.org/netdev/net-next/c/d4b0ad9a8174
- [v2,2/2] dpll: zl3073x: recognize the ZL30643 chip ID (0x0E3B)
https://git.kernel.org/netdev/net-next/c/24e4aff8983f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-06 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 17:35 Vincent Jardin via B4 Relay
2026-07-30 17:35 ` [PATCH v2 1/2] dt-bindings: dpll: zl3073x: ZL30643 is compatible Vincent Jardin via B4 Relay
2026-07-30 18:11 ` Conor Dooley
2026-07-30 17:35 ` [PATCH v2 2/2] dpll: zl3073x: recognize the ZL30643 chip ID (0x0E3B) Vincent Jardin via B4 Relay
2026-08-06 2:10 ` patchwork-bot+netdevbpf [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=178598221489.607412.12370158005617212276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=vjardin@free.fr \
/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
all inboxes | Powered by JetHome®