Re: [PATCH 3.4 00/65] 3.4.110-rc1 review

From: Geert Uytterhoeven
Date: Tue Oct 20 2015 - 05:02:11 EST


On Tue, Oct 20, 2015 at 10:23 AM, Zefan Li <lizefan@xxxxxxxxxx> wrote:
> On 2015/10/20 15:05, Geert Uytterhoeven wrote:
>> On Tue, Oct 20, 2015 at 4:17 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
>>> On 10/19/2015 05:47 PM, lizf@xxxxxxxxxx wrote:
>>>> From: Zefan Li <lizefan@xxxxxxxxxx>
>>>>
>>>> This is the start of the stable review cycle for the 3.4.110 release.
>>>> There are 65 patches in this series, all will be posted as a response
>>>> to this one. If anyone has any issues with these being applied, please
>>>> let me know.
>>>>
>>>
>>> Build results:
>>> total: 97 pass: 96 fail: 1
>>> Failed builds:
>>> m68k:sun3_defconfig
>>>
>>> Qemu test results:
>>> total: 63 pass: 63 fail: 0
>>>
>>> Build failure is due to inconsistent kallsyms data when building
>>> m68k:sun3_defconfig.
>>> From the build log:
>>>
>>> Inconsistent kallsyms data
>>> This is a bug - please report about it
>>> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
>>> Makefile:922: recipe for target 'vmlinux' failed
>>>
>>> Bisect says that the problem is caused by "vfs: Test for and handle paths
>>> that are unreachable from their mnt_root", and reverting that patch
>>> fixes the problem. No idea what is going on. Copying Eric and Geert.
>
> This is odd...

sun3_defconfig builds fine for me with gcc-4.1.2 20061115 (prerelease)
(Ubuntu 4.1.1-21) and with gcc-4.9.0 (kernel.org crosstool).

>> The posted patch is whitespace-damaged. Is there a git tree I can fetch
>> from?
>
> Oops.
>
> The patch is attached. And you can also fetch thost changes from

Thanks, that one applied cleanly.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/