From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stefan Raspl <raspl@linux.ibm.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 3 (net/smc/smc_ism.o)
Date: Tue, 3 Oct 2023 18:08:05 -0700 [thread overview]
Message-ID: <d53b5b50-d894-4df8-8969-fd39e63440ae@infradead.org> (raw)
In-Reply-To: <20231003143340.61697d4c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On 10/2/23 20:33, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230929:
>
on s390: when
CONFIG_ISM=m
CONFIG_SMC=y
s390-linux-ld: net/smc/smc_ism.o: in function `smcd_register_dev':
smc_ism.c:(.text+0x55c): undefined reference to `ism_get_smcd_ops'
s390-linux-ld: net/smc/smc_ism.o: in function `smc_ism_init':
smc_ism.c:(.text+0x1dc2): undefined reference to `ism_register_client'
s390-linux-ld: net/smc/smc_ism.o: in function `smc_ism_exit':
smc_ism.c:(.text+0x1e08): undefined reference to `ism_unregister_client'
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r8109.gz --]
[-- Type: application/gzip, Size: 30465 bytes --]
next parent reply other threads:[~2023-10-04 1:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231003143340.61697d4c@canb.auug.org.au>
2023-10-04 1:08 ` Randy Dunlap [this message]
2023-10-04 12:37 ` linux-next: Tree for Oct 3 (net/smc/smc_ism.o) 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
2023-10-16 23:09 ` Randy Dunlap
2023-10-17 14:15 ` Gerd Bayer
2023-11-14 9:17 ` [PATCH net] s390/ism: ism driver implies smc protocol Gerd Bayer
2023-11-15 10:23 ` Simon Horman
2023-11-15 15:29 ` Gerd Bayer
2023-11-15 15:59 ` [PATCH net v2] " Gerd Bayer
2023-11-15 17:06 ` Simon Horman
2023-11-15 20:43 ` Randy Dunlap
2023-11-17 0:40 ` patchwork-bot+netdevbpf
2023-11-16 8:26 ` [PATCH net] " Wen Gu
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=d53b5b50-d894-4df8-8969-fd39e63440ae@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
/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).