From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux/m68k <linux-m68k@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: drivers/char/dsp56k.c breakage [was: Re: linux-next: Tree for May 26]
Date: Mon, 26 May 2008 16:46:45 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805261644230.4417@anakin> (raw)
In-Reply-To: <20080526172222.b6979523.sfr@canb.auug.org.au>
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@linux-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
next prev parent reply other threads:[~2008-05-26 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 7:22 linux-next: Tree for May 26 Stephen Rothwell
2008-05-26 9:42 ` [BUG] linux-next: Tree for May 26 - kernel oops at __alloc_pages_internal () Kamalesh Babulal
2008-05-26 14:20 ` linux-next: Tree for May 26 Geert Uytterhoeven
2008-05-27 0:51 ` Stephen Rothwell
2008-05-27 3:00 ` Stephen Rothwell
2008-05-26 14:46 ` Geert Uytterhoeven [this message]
2008-05-26 14:56 ` drivers/char/dsp56k.c breakage [was: Re: linux-next: Tree for May 26] Jonathan Corbet
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=Pine.LNX.4.64.0805261644230.4417@anakin \
--to=geert@linux-m68k.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).