From: Heiner Kallweit <hkallweit1@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Sander Vanheule <sander@svanheule.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regmap: remove MDIO support
Date: Wed, 7 May 2025 08:49:15 +0200 [thread overview]
Message-ID: <a975df3f-45a7-426d-8e29-f3b3e2f3f9e7@gmail.com> (raw)
In-Reply-To: <aBr70GkoQEpe0sOt@finisterre.sirena.org.uk>
On 07.05.2025 08:21, Mark Brown wrote:
> On Wed, May 07, 2025 at 08:09:27AM +0200, Heiner Kallweit wrote:
>> On 07.05.2025 02:50, Mark Brown wrote:
>>> On Tue, May 06, 2025 at 10:06:00PM +0200, Heiner Kallweit wrote:
>
>>>> MDIO regmap support was added with 1f89d2fe1607 as only patch from a
>>>> series. The rest of the series wasn't applied. Therefore MDIO regmap
>>>> has never had a user.
>
>>> Is it causing trouble, or is this just a cleanup?
>
>> It's merely a cleanup. The only thing that otherwise would need
>
> If it's not getting in the way I'd rather leave it there in case someone
> wants it, that way I don't need to get CCed into some other series
> again.
>
Understood. On the other hand is has been sitting idle for 4 yrs now.
>> improvement is that REGMAP_MDIO selects MDIO_BUS w/o considering
>> the dependency of MDIO_BUS on MDIO_DEVICE. REGMAP_MDIO should
>> depend on MDIO_BUS.
>
> Well, REGMAP_MDIO should be selected itself so none of these selects or
> dependencies would do anything anyway.
next prev parent reply other threads:[~2025-05-07 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 20:06 Heiner Kallweit
2025-05-07 0:50 ` Mark Brown
2025-05-07 6:09 ` Heiner Kallweit
2025-05-07 6:21 ` Mark Brown
2025-05-07 6:49 ` Heiner Kallweit [this message]
2025-05-07 12:30 ` Andrew Lunn
2025-05-07 20:23 ` Sander Vanheule
2025-05-08 14:32 ` Mark Brown
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=a975df3f-45a7-426d-8e29-f3b3e2f3f9e7@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sander@svanheule.net \
/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®