netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrew Lunn <andrew@lunn.ch>
Cc: robh@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	chaoyi.chen@rock-chips.com, matthias.schiffer@ew.tq-group.com,
	linux@armlinux.org.uk, hkallweit1@gmail.com,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] dt-bindings: net: ethernet-controller: Add informative text about RGMII delays
Date: Tue, 06 May 2025 00:00:53 +0000	[thread overview]
Message-ID: <174648965399.970984.1804246664107675712.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250430-v6-15-rc3-net-rgmii-delays-v2-1-099ae651d5e5@lunn.ch>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 30 Apr 2025 11:21:35 -0500 you wrote:
> Device Tree and Ethernet MAC driver writers often misunderstand RGMII
> delays. Rewrite the Normative section in terms of the PCB, is the PCB
> adding the 2ns delay. This meaning was previous implied by the
> definition, but often wrongly interpreted due to the ambiguous wording
> and looking at the definition from the wrong perspective. The new
> definition concentrates clearly on the hardware, and should be less
> ambiguous.
> 
> [...]

Here is the summary with links:
  - [net,v2] dt-bindings: net: ethernet-controller: Add informative text about RGMII delays
    https://git.kernel.org/netdev/net/c/c360eb0c3ccb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-05-06  0:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 16:21 [PATCH net v2] dt-bindings: net: ethernet-controller: Add informative text about RGMII delays Andrew Lunn
2025-05-01 14:28 ` Conor Dooley
2025-05-06  0:00 ` patchwork-bot+netdevbpf [this message]
2025-05-07  7:17 ` Matthias Schiffer
2025-06-04 10:52 ` Icenowy Zheng
2025-06-04 12:23   ` Andrew Lunn
2025-06-05  9:06     ` Icenowy Zheng
2025-06-05  9:41       ` Russell King (Oracle)
2025-06-05 10:51         ` Icenowy Zheng
2025-06-05 12:44           ` Russell King (Oracle)
2025-06-05 13:48           ` Andrew Lunn
2025-06-11  8:03             ` Icenowy Zheng
2025-06-11  8:39               ` Russell King (Oracle)
2025-06-11 12:11                 ` Icenowy Zheng
2025-06-11 15:28                   ` Andrew Lunn
2025-06-13  8:01                     ` Icenowy Zheng
2025-06-13  8:35                       ` Russell King (Oracle)
2025-06-13  8:43                         ` Icenowy Zheng
2025-06-13  9:05                           ` Russell King (Oracle)
2025-06-11 15:05               ` Andrew Lunn
2025-06-05 13:20         ` Andrew Lunn

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=174648965399.970984.1804246664107675712.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=chaoyi.chen@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).