From: Kyle McMartin <kyle@infradead.org>
To: Kyle McMartin <kyle@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
Richard Henderson <rth@twiddle.net>,
Russell King <rmk@arm.linux.org.uk>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Bryan Wu <cooloney@kernel.org>, Mikael Starvik <starvik@axis.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Tony Luck <tony.luck@intel.com>,
Hirokazu Takata <takata@linux-m32r.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Ungerer <gerg@uclinux.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-parisc@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Jeff Dike <jdike@addtoit.com>, Ingo Molnar <mingo@redhat.com>,
Chris Zankel <chris@zankel.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: setup_arch/arch_get_boot_command_line changes
Date: Tue, 9 Dec 2008 18:33:47 -0500 [thread overview]
Message-ID: <20081209233347.GD7015@bombadil.infradead.org> (raw)
In-Reply-To: <20081209230214.GB7015@bombadil.infradead.org>
On Tue, Dec 09, 2008 at 06:02:14PM -0500, Kyle McMartin wrote:
> On Tue, Dec 09, 2008 at 05:59:31PM -0500, Kyle McMartin wrote:
> > Will this not run afoul of lockdep since it will be attempting to take
> > locks before lockdep has initialized?
> >
>
> Ah, printk calls lockdep_off now. Handy.
>
Nevermind, this doesn't do what I think it does... Rusty, does this work
with lockdep enabled?
next prev parent reply other threads:[~2008-12-09 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 22:20 Rusty Russell
2008-12-09 22:59 ` Kyle McMartin
2008-12-09 23:02 ` Kyle McMartin
2008-12-09 23:33 ` Kyle McMartin [this message]
2008-12-10 12:44 ` Rusty Russell
2008-12-09 23:54 ` Linus Torvalds
2008-12-10 12:27 ` Rusty Russell
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=20081209233347.GD7015@bombadil.infradead.org \
--to=kyle@infradead.org \
--cc=chris@zankel.net \
--cc=cooloney@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hskinnemoen@atmel.com \
--cc=jdike@addtoit.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®