linux-kernel - Re: linux-next: Tree for July 17 (fs/sync.c)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdUwPAx1BO=FAw7sCfa3wU7cwtn6T0hCdkWDGkP8D3T0YQ@mail.gmail.com>
Date:	Tue, 17 Jul 2012 22:51:18 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: linux-next: Tree for July 17 (fs/sync.c)

On Tue, Jul 17, 2012 at 10:29 PM, Randy Dunlap <rdunlap@...otime.net> wrote:
> On 07/16/2012 10:41 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20120716:
>>
>> The vfs tree lost its build failure.
>
>
>
> on i386:
>
> fs/sync.c: In function 'sys_sync':
> fs/sync.c:110:2: error: implicit declaration of function 'iterate_bdevs'
>
>
> Full randconfig file is attached.

According to https://lkml.org/lkml/2012/7/17/61, it happens for
!CONFIG_BLOCK

Also in e.g. sh-allnoconfig,
http://kisskb.ellerman.id.au/kisskb/buildresult/6722464/

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/