From: Lee Jones <lee@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Ivan Vecera <ivecera@redhat.com>,
netdev@vger.kernel.org,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Michal Schmidt <mschmidt@redhat.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v8 1/8] dt-bindings: dpll: Add DPLL device and pin
Date: Tue, 13 May 2025 11:24:51 +0100 [thread overview]
Message-ID: <20250513102451.GI2936510@google.com> (raw)
In-Reply-To: <84410317-6f83-46a9-aa5c-a84947b89f00@linaro.org>
On Thu, 08 May 2025, Krzysztof Kozlowski wrote:
> On 07/05/2025 17:24, Ivan Vecera wrote:
> > Add a common DT schema for DPLL device and its associated pins.
> > The DPLL (device phase-locked loop) is a device used for precise clock
> > synchronization in networking and telecom hardware.
> >
> > The device includes one or more DPLLs (channels) and one or more
> > physical input/output pins.
> >
> One patchset per 24h. You already sent it today and immediately send
> next version without giving time for any actual review.
I just came by to say exactly the same.
There is no rush. Please slow down.
This is not going to be applied for v6.16 and there is much to discuss.
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-05-13 10:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 15:24 [PATCH net-next v8 0/8] Add Microchip ZL3073x support (part 1) Ivan Vecera
2025-05-07 15:24 ` [PATCH net-next v8 1/8] dt-bindings: dpll: Add DPLL device and pin Ivan Vecera
2025-05-08 7:32 ` Krzysztof Kozlowski
2025-05-13 10:24 ` Lee Jones [this message]
2025-05-07 15:24 ` [PATCH net-next v8 2/8] dt-bindings: dpll: Add support for Microchip Azurite chip family Ivan Vecera
2025-05-07 15:24 ` [PATCH net-next v8 3/8] mfd: Add Microchip ZL3073x support Ivan Vecera
2025-05-07 15:25 ` [PATCH net-next v8 4/8] mfd: zl3073x: Add support for devlink device info Ivan Vecera
2025-05-07 15:25 ` [PATCH net-next v8 5/8] mfd: zl3073x: Protect operations requiring multiple register accesses Ivan Vecera
2025-05-07 15:25 ` [PATCH net-next v8 6/8] mfd: zl3073x: Fetch invariants during probe Ivan Vecera
2025-05-07 15:25 ` [PATCH net-next v8 7/8] mfd: zl3073x: Add clock_id field Ivan Vecera
2025-05-07 15:25 ` [PATCH net-next v8 8/8] mfd: zl3073x: Register DPLL sub-device during init Ivan Vecera
2025-05-07 16:13 ` [PATCH net-next v8 0/8] Add Microchip ZL3073x support (part 1) Ivan Vecera
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=20250513102451.GI2936510@google.com \
--to=lee@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=andy@kernel.org \
--cc=arkadiusz.kubalewski@intel.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=horms@kernel.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).