From: Sander Vanheule <sander@svanheule.net>
To: Heiner Kallweit <hkallweit1@gmail.com>
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>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] regmap: remove MDIO support
Date: Wed, 07 May 2025 22:23:49 +0200 [thread overview]
Message-ID: <4cdbc8804ad23a24a9aa3bb12667031b5bada3a6.camel@svanheule.net> (raw)
In-Reply-To: <a975df3f-45a7-426d-8e29-f3b3e2f3f9e7@gmail.com>
Hi Heiner,
On Wed, 2025-05-07 at 08:49 +0200, Heiner Kallweit wrote:
> 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.
How time flies...
The original series that this was part of was never fully merged. This was (in
part) due to some general regmap changes being required [1]. In the meantime
someone else has submitted (nearly the same) changes that were merged into
regmap [2], so I could try resubmitting my patches. These have now been included
downstream in OpenWrt for a few months too, where they are using the regmap MDIO
support, but I understand that out-of-tree consumers aren't usually up for
consideration.
Best,
Sander
[1] https://lore.kernel.org/linux-gpio/cover.1623532208.git.sander@svanheule.net/
[2] https://lore.kernel.org/lkml/20240408101803.43183-2-rf@opensource.cirrus.com/
next prev parent reply other threads:[~2025-05-07 20:29 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
2025-05-07 12:30 ` Andrew Lunn
2025-05-07 20:23 ` Sander Vanheule [this message]
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=4cdbc8804ad23a24a9aa3bb12667031b5bada3a6.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®