public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	driver-core@lists.linux.dev
Subject: [PATCH net-next 0/2] remove Kconfig sysmbol MDIO_BUS
Date: Sun, 15 Mar 2026 17:47:47 +0100	[thread overview]
Message-ID: <bc63cf87-3dba-4ab6-9c84-caa7357c3273@gmail.com> (raw)

MDIO-based regmap is the last user of config symbol MDIO_BUS.
MDIO access needs a MII bus, which requires PHYLIB for the provider part.
Therefore make REGMAP_MDIO depend on PHYLIB, what allows to remove
config symbol MDIO_BUS.

Heiner Kallweit (2):
  regmap: mdio: make it depend on PHYLIB
  net: phy: remove Kconfig sysmbol MDIO_BUS

 drivers/base/regmap/Kconfig | 2 +-
 drivers/net/phy/Kconfig     | 6 ------
 drivers/net/phy/Makefile    | 2 +-
 3 files changed, 2 insertions(+), 8 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-03-15 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 16:47 Heiner Kallweit [this message]
2026-03-15 16:48 ` [PATCH net-next 1/2] regmap: mdio: make it depend on PHYLIB Heiner Kallweit
2026-03-16  0:06   ` Mark Brown
2026-03-17 23:28   ` Jakub Kicinski
2026-03-17 23:45     ` Mark Brown
2026-03-15 16:50 ` [PATCH net-next 2/2] net: phy: remove Kconfig symbol MDIO_BUS Heiner Kallweit
2026-03-19  1:40 ` [PATCH net-next 0/2] remove Kconfig sysmbol MDIO_BUS patchwork-bot+netdevbpf

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=bc63cf87-3dba-4ab6-9c84-caa7357c3273@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=dakr@kernel.org \
    --cc=davem@davemloft.net \
    --cc=driver-core@lists.linux.dev \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rafael@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