[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220317121650.934899-1-michael@walle.cc>
Date: Thu, 17 Mar 2022 13:16:50 +0100
From: Michael Walle <michael@...le.cc>
To: patchwork-bot+netdevbpf@...nel.org
Cc: Divya.Koppera@...rochip.com, UNGLinuxDriver@...rochip.com,
andrew@...n.ch, davem@...emloft.net, devicetree@...r.kernel.org,
hkallweit1@...il.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, linux@...linux.org.uk,
madhuri.sripada@...rochip.com, manohar.puri@...rochip.com,
netdev@...r.kernel.org, richardcochran@...il.com,
robh+dt@...nel.org
Subject: Re: [PATCH net-next 0/3] Add support for 1588 in LAN8814
From: patchwork-bot+netdevbpf@...nel.org
> Here is the summary with links:
> - [net-next,1/3] net: phy: micrel: Fix concurrent register access
> https://git.kernel.org/netdev/net-next/c/4488f6b61480
> - [net-next,2/3] dt-bindings: net: micrel: Configure latency values and timestamping check for LAN8814 phy
> https://git.kernel.org/netdev/net-next/c/2358dd3fd325
> - [net-next,3/3] net: phy: micrel: 1588 support for LAN8814 phy
> https://git.kernel.org/netdev/net-next/c/ece19502834d
I'm almost afraid to ask.. but will this series be reverted (or
the device tree bindings patch)? There were quite a few remarks, even
about the naming of the properties. So, will it be part of the next
kernel release or will it be reverted?
-michael
Powered by blists - more mailing lists