From: Jakub Kicinski <kuba@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Peter Rosin <peda@axentia.se>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Davis <afd@ti.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Heiner Kallweit <hkallweit1@gmail.com>,
kernel test robot <lkp@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Samuel Holland <samuel@sholland.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] mux: mmio: Fix missing CONFIG_REGMAP_MMIO
Date: Fri, 16 May 2025 08:55:01 -0700 [thread overview]
Message-ID: <20250516085501.648794e4@kernel.org> (raw)
In-Reply-To: <3172aba1-77f8-46a7-a967-14fae37f66ea@linaro.org>
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.
prev parent reply other threads:[~2025-05-16 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 14:05 [PATCH] mux: mmio: Fix missing CONFIG_REGMAP_MMIO Krzysztof Kozlowski
2025-05-15 14:14 ` Krzysztof Kozlowski
2025-05-16 0:46 ` Jakub Kicinski
2025-05-15 15:30 ` Arnd Bergmann
2025-05-16 8:16 ` Krzysztof Kozlowski
2025-05-16 8:26 ` Krzysztof Kozlowski
2025-05-16 8:58 ` Krzysztof Kozlowski
2025-05-16 14:30 ` Andrew Davis
2025-05-16 15:55 ` Jakub Kicinski [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=20250516085501.648794e4@kernel.org \
--to=kuba@kernel.org \
--cc=afd@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peda@axentia.se \
--cc=samuel@sholland.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;
as well as URLs for NNTP newsgroup(s).