From: Randy Dunlap <rdunlap@infradead.org>
To: Marek Vasut <marex@denx.de>, Arnd Bergmann <arnd@kernel.org>
Cc: kernel test robot <lkp@intel.com>, Arnd Bergmann <arnd@arndb.de>,
kbuild-all@lists.01.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: (.text.ks8851_probe_common+0x370): undefined reference to `__this_module'
Date: Wed, 24 Feb 2021 08:05:53 -0800 [thread overview]
Message-ID: <2e59ed9d-8618-d846-e2df-caf48c548e81@infradead.org> (raw)
In-Reply-To: <bb6e7759-0600-cbd0-c99c-e053285d094f@denx.de>
On 2/24/21 3:02 AM, Marek Vasut wrote:
> On 2/24/21 9:38 AM, Arnd Bergmann wrote:
>> On Wed, Feb 24, 2021 at 3:38 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> On 2/21/21 10:12 PM, kernel test robot wrote:
>>>> Hi Marek,
>>>>
>>>> FYI, the error/warning still remains.
>>>>
>>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>>> head: 31caf8b2a847214be856f843e251fc2ed2cd1075
>>>> commit: ef3631220d2b3d8d14cf64464760505baa60d6ac net: ks8851: Register MDIO bus and the internal PHY
>>>> date: 7 weeks ago
>>>> config: parisc-randconfig-r034-20210222 (attached as .config)
>>>> compiler: hppa-linux-gcc (GCC) 9.3.0
>>>> reproduce (this is a W=1 build):
>>>> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>>> chmod +x ~/bin/make.cross
>>>> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ef3631220d2b3d8d14cf64464760505baa60d6ac
>>>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>>> git fetch --no-tags linus master
>>>> git checkout ef3631220d2b3d8d14cf64464760505baa60d6ac
>>>> # save the attached .config to linux build tree
>>>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc
>>>>
>>>> If you fix the issue, kindly add following tag as appropriate
>>>> Reported-by: kernel test robot <lkp@intel.com>
>>>>
>>>> All errors (new ones prefixed by >>):
>>>>
>>>> hppa-linux-ld: drivers/net/ethernet/micrel/ks8851_common.o: in function `ks8851_probe_common':
>>>>>> (.text.ks8851_probe_common+0x370): undefined reference to `__this_module'
>>>>>> hppa-linux-ld: (.text.ks8851_probe_common+0x374): undefined reference to `__this_module'
>>>
>>> Hey Arnd-
>>>
>>> I wanted to see if you had any ideas about this problem.
>>>
>>> CONFIG_KS8851=y
>>> CONFIG_KS8851_MLL=m
>>>
>>> The problem is that 2 drivers share some common code, but in one case
>>> the shared code is builtin and for the other driver it is a loadable
>>> module. The common code is first built as builtin, so it does not have
>>> the "__this_module" symbol.
>>
>> This is the patch I sent for it:
>>
>> https://lore.kernel.org/lkml/20210125121937.3900988-1-arnd@kernel.org/T/#u
Thanks!
> I was under the impression that the patch was already applied, wasn't it?
Not that I can see/tell.
--
~Randy
next prev parent reply other threads:[~2021-02-24 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 6:12 kernel test robot
2021-02-24 2:38 ` Randy Dunlap
2021-02-24 8:38 ` Arnd Bergmann
2021-02-24 11:02 ` Marek Vasut
2021-02-24 16:05 ` Randy Dunlap [this message]
2021-04-20 16:59 ` Randy Dunlap
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=2e59ed9d-8618-d846-e2df-caf48c548e81@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=marex@denx.de \
/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®