mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Aleksei Sviridkin <f@lex.la>
Cc: andrew+netdev@lunn.ch, hkallweit1@gmail.com,
	linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	ericwouds@gmail.com, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next v2 0/7] net: mdio: an MDIO device driver for the Airoha EN8811H
Date: Mon, 14 Sep 2026 21:09:13 +0200	[thread overview]
Message-ID: <f7ce35aa-2c3a-4f8e-9f99-e52367ff6bed@lunn.ch> (raw)
In-Reply-To: <20260910204916.1979445-1-f@lex.la>

On Thu, Sep 10, 2026 at 08:49:16PM +0000, Aleksei Sviridkin wrote:
> Two of the things I said I would do turned out not to be doable as
> stated.
> 
> > It is fine. I would also add a select or depends on the PHY driver
> > Kconfig stanza to link it to the MDIO_AIROHA_EN8811H driver.
> 
> Kconfig refuses it:
> 
>   symbol AIR_EN8811H_PHY is implied by MDIO_AIROHA_EN8811H
>   symbol MDIO_AIROHA_EN8811H is implied by AIR_EN8811H_PHY
>   error: recursive dependency detected!

O.K. So there is a linkage anyway.

> > The location is fine. MAINTAINERS need to list it. What you might want
> > to do is list it twice, once in the PHY driver MAINTAINERS record, and
> > again in the MDIO driver section.
> 
> There is no PHY driver record to put it in. Neither air_en8811h.c nor
> the shared air_phy_lib.c is claimed by any entry, so the header sits in
> the MDIO record alone. I can add a record covering both files, but that
> puts my name on code I did not write. Tell me which you would rather
> see.

That not great.

$ ./scripts/get_maintainer.pl drivers/net/phy/air_en8811h.c
Andrew Lunn <andrew@lunn.ch> (maintainer:ETHERNET PHY LIBRARY)
Heiner Kallweit <hkallweit1@gmail.com> (maintainer:ETHERNET PHY LIBRARY)
Russell King <linux@armlinux.org.uk> (reviewer:ETHERNET PHY LIBRARY)
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
Eric Dumazet <edumazet@google.com> (maintainer:NETWORKING DRIVERS)
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS)
Paolo Abeni <pabeni@redhat.com> (maintainer:NETWORKING DRIVERS)

The usual generic suspects. Turning on some knobs you can additionally
get:

"Bjørn Mork" <bjorn@mork.no> (commit_signer:3/9=33%,authored:3/9=33%,added_lines:412/668=62%,removed_lines:34/318=11%)
Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com> (commit_signer:3/9=33%,authored:3/9=33%,added_lines:58/668=9%,removed_lines:258/318=81%)

Maybe reach out an see if they want to be listed as Maintainer.

      Andrew

      reply	other threads:[~2026-09-14 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 15:57 Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 1/7] dt-bindings: net: add Airoha EN8811H PHY MCU Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 2/7] net: phy: add mdiodev_lock(), mdiodev_lock_nested() and mdiodev_unlock() Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 3/7] net: phy: air: type the buckpbus core on the mdio device Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 4/7] net: phy: air: move the EN8811H firmware download into the library Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 5/7] net: phy: air: skip the download when the MD32 is already running Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 6/7] net: mdio: add Airoha EN8811H MDIO device driver Aleksei Sviridkin
2026-09-08 15:57 ` [RFC PATCH net-next v2 7/7] net: mdio: en8811h: add the nested bus Aleksei Sviridkin
2026-09-09 19:01 ` [RFC PATCH net-next v2 0/7] net: mdio: an MDIO device driver for the Airoha EN8811H Andrew Lunn
2026-09-10 15:38   ` Aleksei Sviridkin
     [not found]   ` <20260910153757.2822676-1-f@lex.la>
2026-09-10 20:49     ` Aleksei Sviridkin
2026-09-14 19:09       ` Andrew Lunn [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=f7ce35aa-2c3a-4f8e-9f99-e52367ff6bed@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=ericwouds@gmail.com \
    --cc=f@lex.la \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --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

all inboxes | Powered by JetHome®