From: Jakub Kicinski <kuba@kernel.org>
To: "Ilya A. Evenbach" <ievenbach@aurora.tech>
Cc: netdev@vger.kernel.org, dima.fedrau@gmail.com
Subject: Re: [PATCH] [88q2xxx] Add support for handling master/slave in forced mode
Date: Wed, 20 Aug 2025 17:35:28 -0700 [thread overview]
Message-ID: <20250820173528.68a5c33d@kernel.org> (raw)
In-Reply-To: <20250820181143.2288755-2-ievenbach@aurora.tech>
A few drive-by comments...
On Wed, 20 Aug 2025 11:11:43 -0700 Ilya A. Evenbach wrote:
> In-Reply-To: <20250820181143.2288755-1-ievenbach@aurora.tech>
Please start a new thread for each new revision.
Change subject to [PATCH vN], where vN is the revision.
Add
v1: https://lore.kernel.org/20250820181143.2288755-2-ievenbach@aurora.tech
under the --- for reference to older versions
> Cc: dima.fedrau@gmail.com, "Ilya A. Evenbach" <ievenbach@aurora.tech>
The cc list is still pretty sparse
> Subject: [PATCH] [88q2xxx] Add support for handling master/slave in forced mode
the [88q2xxx] will be stripped by git when applying. Please look thru
the history of the file and find the correct way to prefix.
> 88q2xxx PHYs have non-standard way of setting master/slave in
> forced mode.
> This change adds support for changing and reporting this setting
> correctly through ethtool.
imperative mood:
Add support for changing...
> +/* Marvell vendor PMA/PMD control for forced master/slave when AN is disabled */
> +#define PMAPMD_MVL_PMAPMD_CTL 0x0834
> +#define MASTER_MODE BIT(14)
> +#define MODE_MASK BIT(14)
Other defines in context seem to be prefixed with MV88Q2XXX_
please prefer prefixing local defines.
> struct mv88q2xxx_priv {
> bool enable_led0;
> };
> @@ -377,13 +382,57 @@ static int mv88q2xxx_read_link(struct phy_device *phydev)
> static int mv88q2xxx_read_master_slave_state(struct phy_device *phydev)
> {
> int ret;
> + int adv_l, adv_m, stat, stat2;
nit: in networking we like variable declaration lines to be sorted longest to shortest.
--
pw-bot: cr
next prev parent reply other threads:[~2025-08-21 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 21:29 [PATCH] [88q2xxx] Add support for handling master/slave in forced mode Ilya A. Evenbach
2025-08-19 22:13 ` Andrew Lunn
2025-08-20 18:11 ` Ilya A. Evenbach
2025-08-20 18:11 ` [PATCH] [88q2xxx] Add support for handling master/slave in forced mode Ilya A. Evenbach
2025-08-21 0:35 ` Jakub Kicinski [this message]
2025-08-21 8:02 ` Dimitri Fedrau
[not found] ` <CAJmffrpUTzH0_siTUZodX7Gu5JPRvkgUb+73CgXSWu1QSzegSA@mail.gmail.com>
2025-08-22 6:58 ` Dimitri Fedrau
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=20250820173528.68a5c33d@kernel.org \
--to=kuba@kernel.org \
--cc=dima.fedrau@gmail.com \
--cc=ievenbach@aurora.tech \
--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 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).