linux-kernel - drivers/char/dsp56k.c breakage [was: Re: linux-next: Tree for May 26]

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.0805261644230.4417@anakin>
Date:	Mon, 26 May 2008 16:46:45 +0200 (CEST)
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Jonathan Corbet <corbet@....net>
cc:	linux-next@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Linux/m68k <linux-m68k@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: drivers/char/dsp56k.c breakage [was: Re: linux-next: Tree for May
 26]

On Mon, 26 May 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.

commit	6fe28df6c14e7e02bfea6b2bebf42716176e6dff

    dsp56k: BKL pushdown

    Put explicit lock_kernel calls into dsp56k_open().

Broke the build of drivers/char/dsp56k.c by introducing a jump to a
non-existent label

http://kisskb.ellerman.id.au/kisskb/buildresult/29211/

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/