From: Thomas Meyer <thomas@m3y3r.de>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Vegard Nossum <vegard.nossum@gmail.com>,
Pekka Enberg <penberg@cs.helsinki.fi>, Greg KH <gregkh@suse.de>,
kexec <kexec@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
kernel-testers@vger.kernel.org, Bernhard Walle <bwalle@suse.de>,
Vivek Goyal <vgoyal@redhat.com>
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-07-20 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080718195352.e562a00f.sfr@canb.auug.org.au>
[not found] ` <200807190928.33978.m.kozlowski@tuxland.pl>
[not found] ` <19f34abd0807190255x304173d4wf2bfabb2d5bce511@mail.gmail.com>
[not found] ` <19f34abd0807190559y2fe5ebf9h7095793e82de3122@mail.gmail.com>
[not found] ` <20080719221723.GB5578@suse.de>
[not found] ` <19f34abd0807191527u61c5ed61kffe2279c8d46915d@mail.gmail.com>
[not found] ` <19f34abd0807191544nfd73be5nf7dde4b61992a7e8@mail.gmail.com>
[not found] ` <20080719225817.GA6264@suse.de>
[not found] ` <19f34abd0807191611y7cabf405iad307ba79591e04f@mail.gmail.com>
2008-07-20 9:01 ` linux-next: Tree for July 18: warning at kernel/lockdep.c:2068 trace_hardirqs_on_caller 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 13:47 ` Bernhard Walle
2008-07-21 14:54 ` Vivek Goyal
2008-07-21 15:00 ` Bernhard Walle
2008-07-21 15:00 ` Bernhard Walle
2008-07-22 6:15 ` Yasunori Goto
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