From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 net-next] net: phy: Drop #inclusion of <linux/mod_devicetable.h> from <linux/mdio.h>
Date: Tue, 7 Jul 2026 09:15:35 +0200 [thread overview]
Message-ID: <akynGw4TQimFiQST@monoceros> (raw)
In-Reply-To: <96a77bc9-9804-43fb-acf0-b93574cd60f3@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hello Andrew,
On Mon, Jul 06, 2026 at 11:28:33PM +0200, Andrew Lunn wrote:
> > That's exactly my thought, and there is commit ad428f5811bd
> > ("mod_devicetable.h: Split into per subsystem headers") that is part of
> > v7.2-rc2 and that does exactly that (apart from the filename).
>
> Ah, O.K. net-next tends to great dragged along the -rcX versions. So
> you can probably submit the networking changes in a weeks time. Just
> make sure they apply to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
Note that while I created the patch under discussion on top of -rc2, the
justification is also valid on -rc1 and the patch doesn't use the new
headers, so it can be applied to the above repo already now.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-07 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:29 [PATCH v1 net-next] net: phy: Drop #inclusion of <linux/mod_devicetable.h> from <linux/mdio.h> Uwe Kleine-König (The Capable Hub)
2026-07-06 14:17 ` Andrew Lunn
2026-07-06 20:48 ` Uwe Kleine-König (The Capable Hub)
2026-07-06 21:28 ` Andrew Lunn
2026-07-07 7:15 ` Uwe Kleine-König (The Capable Hub) [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=akynGw4TQimFiQST@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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