From: Jakub Kicinski <kuba@kernel.org>
To: "Kamil Horák - 2N" <kamilh@axis.com>
Cc: <florian.fainelli@broadcom.com>,
<bcm-kernel-feedback-list@broadcom.com>, <andrew@lunn.ch>,
<hkallweit1@gmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode
Date: Fri, 14 Jun 2024 18:07:14 -0700 [thread overview]
Message-ID: <20240614180714.7f81a9cd@kernel.org> (raw)
In-Reply-To: <20240613132055.49207-1-kamilh@axis.com>
On Thu, 13 Jun 2024 15:20:51 +0200 Kamil Horák - 2N wrote:
> 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
Doesn't build..
drivers/net/phy/phy-core.c:16:2: error: call to '__compiletime_assert_1283' declared with 'error' attribute: Enum ethtool_link_mode_bit_indices and phylib are out of sync. If a speed or mode has been added please update phy_speed_to_str and the PHY settings array.
16 | BUILD_BUG_ON_MSG(__ETHTOOL_LINK_MODE_MASK_NBITS != 102,
| ^
prev parent reply other threads:[~2024-06-15 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:20 [PATCH v6 0/4] net: phy: bcm5481x: add support for BroadR-Reach mode Kamil Horák - 2N
2024-06-13 13:20 ` [PATCH v6 1/4] net: phy: bcm54811: New link mode for BroadR-Reach Kamil Horák - 2N
2024-06-13 13:20 ` [PATCH v6 2/4] net: phy: bcm54811: Add LRE registers definitions Kamil Horák - 2N
2024-06-13 13:20 ` [PATCH v6 3/4] dt-bindings: ethernet-phy: add optional brr-mode flag Kamil Horák - 2N
2024-06-14 8:12 ` Krzysztof Kozlowski
2024-06-13 13:20 ` [PATCH v6 4/4] net: phy: bcm-phy-lib: Implement BroadR-Reach link modes Kamil Horák - 2N
2024-06-15 1:07 ` Jakub Kicinski [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=20240614180714.7f81a9cd@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.