linux-kernel - Re: linux-next: Tree for April 24

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: <Pine.LNX.4.64.0804242136420.21224@anakin>
Date:	Thu, 24 Apr 2008 21:40:15 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Christoph Hellwig <hch@...radead.org>
cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	xfs@....sgi.com
Subject: Re: linux-next: Tree for April 24

On Thu, 24 Apr 2008, Stephen Rothwell wrote:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next.  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.

For the second day in a row, m68k builds failed because of

    fs/xfs/xfs_fsops.c:527: error: implicit declaration of function 'xfs_icsb_sync_counters_locked'
    make[3]: *** [fs/xfs/xfs_fsops.o] Error 1

According to
http://www.linux.sgi.com/archives/xfs/2008-03/msg00202.html, there's a
forward declaration for xfs_icsb_sync_counters_locked() only if HAVE_PERCPU_SB
is defined, i.e. for CONFIG_SMP. This break UP architectures.

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/