From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
hkelam@marvell.com, davem@davemloft.net, kuba@kernel.org,
naveenm@marvell.com, arnd@arndb.de, colin.king@canonical.com,
yig@marvell.com, zhengyongjun3@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] octeontx2-nic: fix mixed module build
Date: Mon, 18 Oct 2021 12:20:07 +0000 [thread overview]
Message-ID: <163455960701.13509.15630125332041765591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211015210616.884437-1-arnd@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 15 Oct 2021 23:06:01 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Building the VF and PF side of this driver differently, with one being
> a loadable module and the other one built-in results in a link failure
> for the common PTP driver:
>
> ld.lld: error: undefined symbol: __this_module
> >>> referenced by otx2_ptp.c
> >>> net/ethernet/marvell/octeontx2/nic/otx2_ptp.o:(otx2_ptp_init) in archive drivers/built-in.a
> >>> referenced by otx2_ptp.c
> >>> net/ethernet/marvell/octeontx2/nic/otx2_ptp.o:(otx2_ptp_init) in archive drivers/built-in.a
>
> [...]
Here is the summary with links:
- [net-next] octeontx2-nic: fix mixed module build
https://git.kernel.org/netdev/net-next/c/0e9e7598c68f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-18 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 21:06 [PATCH net-next] octeontx2-nic: fix mixed module build Arnd Bergmann
2021-10-18 12:20 ` patchwork-bot+netdevbpf [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=163455960701.13509.15630125332041765591.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=yig@marvell.com \
--cc=zhengyongjun3@huawei.com \
/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