From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: v2.6.25: WARNING: at kernel/lockdep.c:2437 __lock_acquire+0xc69/0xfa0()
Date: Sun, 12 Apr 2009 11:11:37 -0700 [thread overview]
Message-ID: <49E22ED9.40100@gmail.com> (raw)
In-Reply-To: <49E0C102.4020705@pobox.com>
Jeff Garzik wrote:
> (going through old, unresolved email)
>
> It looks like this might still be needed? I never saw an "it works"
> response to this email.
Indeed. Peter Zijlstra, can you please test it?
--
tejun
next prev parent reply other threads:[~2009-04-13 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19f34abd0804200329j3308b081vc0732c3ec5c0b721@mail.gmail.com>
[not found] ` <1208782090.7115.179.camel@twins>
2008-04-24 3:01 ` v2.6.25: WARNING: at kernel/lockdep.c:2437 __lock_acquire+0xc69/0xfa0() Tejun Heo
2009-04-11 16:10 ` Jeff Garzik
2009-04-12 18:11 ` Tejun Heo [this message]
2009-04-14 3:59 ` [PATCH #upstream-fixes] pata_legacy: fix no device fail path Tejun Heo
2009-04-16 19:23 ` Jeff Garzik
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=49E22ED9.40100@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=vegard.nossum@gmail.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;
as well as URLs for NNTP newsgroup(s).