From: Rusty Russell <rusty@rustcorp.com.au>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: rpjday@crashcourse.ca, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at kernel/workqueue.c:169 (was: linux-next: Tree for June 16)
Date: Mon, 23 Jun 2008 13:15:54 +1000 [thread overview]
Message-ID: <200806231315.54490.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1213987718.3134.7.camel@dhcppc4>
On Saturday 21 June 2008 04:48:37 Thomas Meyer wrote:
> I tried to bisect this one, but without a consistent result.
That's always suspicious...
> Another thing i tried is to change <linux/kernel.h>:
This will also cause almost everything to be rebuilt. I find it hard to
believe this is the culprit; does a "make clean" also fix it?
Thanks,
Rusty.
next prev parent reply other threads:[~2008-06-23 3:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 9:01 linux-next: Tree for June 16 Stephen Rothwell
2008-06-16 21:28 ` kernel BUG at kernel/workqueue.c:169 (was: linux-next: Tree for June 16) Thomas Meyer
2008-06-20 18:48 ` Thomas Meyer
2008-06-23 3:15 ` Rusty Russell [this message]
2008-06-23 20:10 ` Thomas Meyer
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=200806231315.54490.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=thomas@m3y3r.de \
/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).