[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nKJBVsuvqr17qa0xnkQTUz9aaAGRi8SfXZAn-G=RYQXw@mail.gmail.com>
Date: Sat, 20 Mar 2021 07:07:57 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Stephen Rothwell <sfr@...hwell.id.au>
Cc: Heiko Carstens <hca@...ux.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Alex Gaynor <alex.gaynor@...il.com>,
Geoffrey Thomas <geofft@...reload.com>,
Finn Behrens <me@...enk.de>,
Wedson Almeida Filho <wedsonaf@...gle.com>,
Adam Bratschi-Kaye <ark.email@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Vasily Gorbik <gor@...ux.ibm.com>,
Christian Borntraeger <borntraeger@...ibm.com>,
Daniel Axtens <dja@...ens.net>
Subject: Re: linux-next: Tree for Mar 19
On Sat, Mar 20, 2021 at 6:33 AM Stephen Rothwell <sfr@...hwell.id.au> wrote:
>
> 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 ...
Sorry for that, and thanks a lot for taking a look. For the Rust
support I had to increase a few limits, mainly the symbol length. Let
me check and I'll report back.
Cheers,
Miguel
Powered by blists - more mailing lists