[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250516085501.648794e4@kernel.org>
Date: Fri, 16 May 2025 08:55:01 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Peter Rosin <peda@...ntia.se>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Andrew Davis
<afd@...com>, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Heiner
Kallweit <hkallweit1@...il.com>, kernel test robot <lkp@...el.com>, Greg
Kroah-Hartman <gregkh@...uxfoundation.org>, Samuel Holland
<samuel@...lland.org>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] mux: mmio: Fix missing CONFIG_REGMAP_MMIO
On Fri, 16 May 2025 10:58:38 +0200 Krzysztof Kozlowski wrote:
> My branch fails with above error because I do not have Heiner's commit
> a3e1c0ad8357 ("net: phy: factor out provider part from mdio_bus.c").
> Will it reach current RC (rc7) at some point?
No :( We merged it to net-next, so it will have to wait until the merge
window. Worst case you can double apply that change? Maybe git will be
clever enough to auto-resolve. Obviously only if absolutely necessary..
We could also try to sequence our PRs to Linus so that your changes
are rebased after net-next merge. We send our PR in the first day or
two of the MW.
Powered by blists - more mailing lists