From: Thomas Meyer <thomas@m3y3r.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Vegard Nossum <vegard.nossum@gmail.com>, Greg KH <gregkh@suse.de>,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
Stephen Rothwell <sfr@canb.auug.org.au>,
kernel-testers@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Bernhard Walle <bwalle@suse.de>, Ingo Molnar <mingo@elte.hu>,
Vivek Goyal <vgoyal@redhat.com>,
kexec <kexec@lists.infradead.org>
Subject: Re: linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller
Date: Sun, 20 Jul 2008 11:35:46 +0200 [thread overview]
Message-ID: <1216546546.3217.0.camel@dhcppc2> (raw)
In-Reply-To: <1216544462.9311.20.camel@nimitz>
Am Sonntag, den 20.07.2008, 02:01 -0700 schrieb Dave Hansen:
> On Sun, 2008-07-20 at 01:11 +0200, Vegard Nossum wrote:
> > Maybe the firmware memmap code can simply run a little later in the
> > boot sequence?
>
> Heh, I'm catching up on this thread...
>
On that thread?
http://lkml.org/lkml/2008/7/15/108
next prev parent reply other threads:[~2008-07-20 9:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 9:53 linux-next: Tree for July 18 Stephen Rothwell
2008-07-19 7:28 ` linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller Mariusz Kozlowski
2008-07-19 9:55 ` Vegard Nossum
2008-07-19 12:56 ` Pekka Enberg
2008-07-19 12:59 ` Vegard Nossum
2008-07-19 13:22 ` Stephen Rothwell
2008-07-19 22:17 ` Greg KH
2008-07-19 22:27 ` Vegard Nossum
2008-07-19 22:41 ` Greg KH
2008-07-19 22:44 ` Vegard Nossum
2008-07-19 22:58 ` Greg KH
2008-07-19 23:11 ` Vegard Nossum
2008-07-19 23:20 ` Greg KH
2008-07-20 12:51 ` Bernhard Walle
2008-07-20 9:01 ` Dave Hansen
2008-07-20 9:35 ` Thomas Meyer [this message]
2008-07-20 13:03 ` Bernhard Walle
2008-07-20 15:44 ` Bernhard Walle
2008-07-21 13:17 ` Vivek Goyal
2008-07-21 13:25 ` Bernhard Walle
2008-07-21 13:39 ` Vivek Goyal
2008-07-21 15:00 ` Bernhard Walle
2008-07-22 6:15 ` Yasunori Goto
2008-07-20 12:48 ` Bernhard Walle
2008-07-19 7:39 ` linux-next: Tree for July 18: nfs problems Mariusz Kozlowski
2008-07-19 9:35 ` linux-next: Tree for July 18: powerpc g3 hangs Mariusz Kozlowski
2008-07-19 15:31 ` linux-next: Tree for July 18 (very early crash on x86_32) Bartlomiej Zolnierkiewicz
2008-07-20 0:20 ` linux-next: Tree for July 18: sky2 WOL broken Rafael J. Wysocki
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=1216546546.3217.0.camel@dhcppc2 \
--to=thomas@m3y3r.de \
--cc=bwalle@suse.de \
--cc=dave@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=kernel-testers@vger.kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.kozlowski@tuxland.pl \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.au \
--cc=vegard.nossum@gmail.com \
--cc=vgoyal@redhat.com \
/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