From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Kamil Horák - 2N" <kamilh@axis.com>,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode
Date: Wed, 19 Jun 2024 16:05:48 +0100 [thread overview]
Message-ID: <85ca3410-6124-41b9-bb39-89659df16615@broadcom.com> (raw)
In-Reply-To: <20240619150359.311459-1-kamilh@axis.com>
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
On 6/19/2024 4:03 PM, Kamil Horák - 2N wrote:
> PATCH 1 - Add the 10baseT1BRR_Full link mode
>
> PATCH 2 - Add the definitions of LRE registers, necessary to use
> BroadR-Reach modes on the BCM5481x PHY
>
> PATCH 3 - Add brr-mode flag to switch between IEEE802.3 and BroadR-Reach
>
> PATCH 4 - Implementation of the BroadR-Reach modes for the Broadcom
> PHYs
>
> Changes in v2:
> - Divided into multiple patches, removed useless link modes
>
> Changes in v3:
> - Fixed uninitialized variable in bcm5481x_config_delay_swap function
>
> Changes in v4:
> - Improved the division of functions between bcm-phy library and broadcom.c
> - Changed the BroadR-Reach / IEEE mode switching to device tree boolean as
> these modes are mutually exclusive and barely could coexist in one hardware
> - Made the link mode selection compatible with current ethtool (i.e. the
> linkmode is selected by choosing speed and master-slave)
>
> Changes in v5:
> - Fixed the operator precedence as reported by the kernel test robot
> - Fixed doc of bcm_linkmode_adv_to_mii_adv_t function
>
> Changes in v6:
> - Moved the brr-mode flag to separate commit as required by the rules for
> DT binding patches
> - Renamed some functions to make clear they handle LRE-related stuff
> - Reordered variable definitions to match the coding style requirements
>
> Changes in v7:
> - Fixed the changes distribution into patches (first one was not buildable)
>
> Changes in v8:
> - Fixed coding style and did other changes on behalf of the reviewers
You got some Acked-by/Reviewed-by tags from reviewers from the previous
version, why were not those carried over?
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2024-06-19 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 15:03 [PATCH v8 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode Kamil Horák - 2N
2024-06-19 15:03 ` [PATCH v8 1/4] net: phy: bcm54811: New link mode for BroadR-Reach Kamil Horák - 2N
2024-06-19 15:03 ` [PATCH v8 2/4] net: phy: bcm54811: Add LRE registers definitions Kamil Horák - 2N
2024-06-19 15:03 ` [PATCH v8 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag Kamil Horák - 2N
2024-06-19 17:36 ` Conor Dooley
2024-06-19 23:38 ` Jakub Kicinski
2024-06-20 7:56 ` Conor Dooley
2024-06-20 12:59 ` Andrew Lunn
2024-06-20 13:35 ` Jakub Kicinski
2024-06-20 13:59 ` Conor Dooley
2024-06-19 15:03 ` [PATCH v8 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach link modes Kamil Horák - 2N
2024-06-19 15:05 ` Florian Fainelli [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=85ca3410-6124-41b9-bb39-89659df16615@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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