From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "kernel test robot" <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Christian Marangi" <ansuelsmth@gmail.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>
Subject: Re: [lunn:v6.3-rc2-net-next-phy-leds 5/15] ld.lld: error: undefined symbol: devm_mdiobus_alloc_size
Date: Thu, 20 Apr 2023 17:39:56 +0200 [thread overview]
Message-ID: <73674ffd-3231-4ca8-af65-3ec621de5072@app.fastmail.com> (raw)
In-Reply-To: <2e7f5511-08e2-4ee0-ab3f-481ba6724824@lunn.ch>
On Thu, Apr 20, 2023, at 17:26, Andrew Lunn wrote:
>> I think the best way is to drop your MDIO_DEVRES patch and instead
>> apply mine (or some variation of that) from
>>
>> https://lore.kernel.org/lkml/20230420084624.3005701-1-arnd@kernel.org/
>>
>> Once any missing or recursive dependencies are handled, the devres
>> problem should be fixed as well. I have completed around 150
>> randconfig builds with that patch and have not seen any further
>> problems.
>
> Is this on top of my patch? Or does it require mine is reverted? I
> can send a revert if it is needed.
The two are independent. I think your patch does nothing once
mine is applied, since the indirect 'select MDIO_DEVRES' will
work again. Reverting it might help avoid some confusion though.
Arnd
prev parent reply other threads:[~2023-04-20 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202303241935.xRMa6mc6-lkp@intel.com>
2023-04-20 6:31 ` Arnd Bergmann
2023-04-20 13:07 ` Andrew Lunn
2023-04-20 13:37 ` Arnd Bergmann
2023-04-20 15:26 ` Andrew Lunn
2023-04-20 15:39 ` Arnd Bergmann [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=73674ffd-3231-4ca8-af65-3ec621de5072@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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®