From: patchwork-bot+netdevbpf@kernel.org
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: rdunlap@infradead.org, wenjia@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
netdev@vger.kernel.org, raspl@linux.ibm.com,
sfr@canb.auug.org.au, alibuda@linux.alibaba.com,
wintera@linux.ibm.com, guwen@linux.alibaba.com,
tonylu@linux.alibaba.com, jaka@linux.ibm.com
Subject: Re: [PATCH net] net/smc: Fix dependency of SMC on ISM
Date: Tue, 10 Oct 2023 10:20:25 +0000 [thread overview]
Message-ID: <169693322510.26630.14172040587036609321.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231006125847.1517840-1-gbayer@linux.ibm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 6 Oct 2023 14:58:47 +0200 you wrote:
> When the SMC protocol is built into the kernel proper while ISM is
> configured to be built as module, linking the kernel fails due to
> unresolved dependencies out of net/smc/smc_ism.o to
> ism_get_smcd_ops, ism_register_client, and ism_unregister_client
> as reported via the linux-next test automation (see link).
> This however is a bug introduced a while ago.
>
> [...]
Here is the summary with links:
- [net] net/smc: Fix dependency of SMC on ISM
https://git.kernel.org/netdev/net/c/a72178cfe855
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-10-10 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 3:33 linux-next: Tree for Oct 3 Stephen Rothwell
2023-10-04 1:08 ` linux-next: Tree for Oct 3 (net/smc/smc_ism.o) Randy Dunlap
2023-10-04 12:37 ` Wenjia Zhang
2023-10-06 12:58 ` [PATCH net] net/smc: Fix dependency of SMC on ISM Gerd Bayer
2023-10-06 14:48 ` Simon Horman
2023-10-06 20:05 ` Randy Dunlap
2023-10-10 10:20 ` patchwork-bot+netdevbpf [this message]
2023-10-16 23:09 ` Randy Dunlap
2023-10-17 14:15 ` Gerd Bayer
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=169693322510.26630.14172040587036609321.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=gbayer@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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