From: Stephen Rothwell <sfr@rothwell.id.au>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Alex Gaynor <alex.gaynor@gmail.com>,
Geoffrey Thomas <geofft@ldpreload.com>,
Finn Behrens <me@kloenk.de>,
Wedson Almeida Filho <wedsonaf@google.com>,
Adam Bratschi-Kaye <ark.email@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Daniel Axtens <dja@axtens.net>
Subject: Re: linux-next: Tree for Mar 19
Date: Sat, 20 Mar 2021 16:27:34 +1100 [thread overview]
Message-ID: <20210320162734.1630cc55@elm.ozlabs.ibm.com> (raw)
In-Reply-To: <YFS1h6h+71sRlwFR@osiris>
Hi all,
On Fri, 19 Mar 2021 15:30:31 +0100 Heiko Carstens <hca@linux.ibm.com> wrote:
>
> This breaks now on s390 with commit 8ef6f74a3571 ("Rust support").
> make modules_install / depmod now fails with:
>
> depmod: WARNING: /.../lib/modules/5.12.0-rc3-00001-g8ef6f74a3571/kernel/drivers/s390/scsi/zfcp.ko needs unknown symbol
>
> for every module (yes, the line is complete).
Daniel Axtens reported the same breakage on powerpc. I bisected it to
the same commit. More experimentation shows that if you reverse just
the change to include/linux/moduleparam.h the above warnings go away.
So
-#define MAX_PARAM_PREFIX_LEN (256 - sizeof(unsigned long))
+#define MAX_PARAM_PREFIX_LEN (64 - sizeof(unsigned long))
fixes it up. Not sure what that does to the rust support ...
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2021-03-20 5:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 6:59 linux-next: Tree for Mar 19 Stephen Rothwell
2021-03-19 14:30 ` Heiko Carstens
2021-03-20 5:27 ` Stephen Rothwell [this message]
2021-03-20 6:07 ` Miguel Ojeda
2021-03-20 6:49 ` Miguel Ojeda
2021-03-20 6:58 ` Miguel Ojeda
2021-03-21 12:30 ` Michael Ellerman
2021-03-21 15:57 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 1:49 Stephen Rothwell
2020-03-19 7:39 Stephen Rothwell
2019-03-19 5:12 Stephen Rothwell
2018-03-19 8:02 Stephen Rothwell
2015-03-19 7:28 Stephen Rothwell
2014-03-19 7:18 Stephen Rothwell
2013-03-19 5:42 Sedat Dilek
2013-03-19 5:47 ` Stephen Rothwell
2013-03-19 5:53 ` Sedat Dilek
2013-03-19 5:54 ` Stephen Rothwell
2013-03-19 6:00 ` Sedat Dilek
2013-03-19 10:24 ` Sedat Dilek
2013-03-19 4:14 Stephen Rothwell
2012-03-19 7:48 Stephen Rothwell
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=20210320162734.1630cc55@elm.ozlabs.ibm.com \
--to=sfr@rothwell.id.au \
--cc=alex.gaynor@gmail.com \
--cc=ark.email@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=dja@axtens.net \
--cc=geofft@ldpreload.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=me@kloenk.de \
--cc=ojeda@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wedsonaf@google.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;
as well as URLs for NNTP newsgroup(s).