From: Zefan Li <lizefan@huawei.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: v3.4-stable-queue build errors
Date: Mon, 15 Jun 2015 14:32:04 +0800 [thread overview]
Message-ID: <557E7164.4000501@huawei.com> (raw)
In-Reply-To: <557E5A87.8020703@roeck-us.net>
On 2015/6/15 12:54, Guenter Roeck wrote:
> On 06/14/2015 08:23 PM, Zefan Li wrote:
>> On 2015/6/13 13:34, Guenter Roeck wrote:
>>> kernel/printk.c: In function 'register_console':
>>> kernel/printk.c:1501:3: error: size of unnamed array is negative
>>> BUILD_BUG_ON(sizeof(console_cmdline[i].name) != sizeof(newcon->name));
>>>
>>> All architectures / builds are affected.
>>>
>>> Caused by 'console: Fix console name size mismatch', which introduces
>>> the BUILD_BUG_ON (but nothing else). Looks like the actual name length
>>> increase in struct console_cmdline (in kernel/printk.c) got lost.
>>>
>>
>> Now should be fixed. Don't know how that happened..
>>
>
> This problem is gone, but there is another problem.
>
> Building alpha:defconfig ... failed
> --------------
> Error log:
> mm/slub.c: In function 'unfreeze_partials':
> mm/slub.c:1920:7: error: 'm' undeclared (first use in this function)
> mm/slub.c:1920:7: note: each undeclared identifier is reported only once for each function it appears in
> mm/slub.c:1920:12: error: 'M_FREE' undeclared (first use in this function)
> make[1]: *** [mm/slub.o] Error 1
>
> This affects most of the builds.
>
I just backported a slub fix but forgot the last chunk.. My config enables slab
instead of slub, so I didn't catch this.
Now should be fixed. Thanks again.
next prev parent reply other threads:[~2015-06-15 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 5:34 v3.4-stable-queue build errors Guenter Roeck
2015-06-15 3:23 ` Zefan Li
2015-06-15 4:54 ` Guenter Roeck
2015-06-15 6:32 ` Zefan Li [this message]
2015-06-15 13:34 ` Guenter Roeck
2015-06-16 2:52 ` Zefan Li
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=557E7164.4000501@huawei.com \
--to=lizefan@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.