From: Sachin Sant <sachinp@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.34-rc3: Badness at kernel/lockdep.c:2706
Date: Sat, 03 Apr 2010 14:04:41 +0530 [thread overview]
Message-ID: <4BB6FDA1.3070502@in.ibm.com> (raw)
In-Reply-To: <m14ojtrjbv.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Could you try the fix Wolfram Sang sent to linux-kernel yesterday?
>
Yes that fixed the issue for me. Thanks Eric.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@in.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: 2.6.34-rc3: Badness at kernel/lockdep.c:2706
Date: Sat, 03 Apr 2010 14:04:41 +0530 [thread overview]
Message-ID: <4BB6FDA1.3070502@in.ibm.com> (raw)
In-Reply-To: <m14ojtrjbv.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Could you try the fix Wolfram Sang sent to linux-kernel yesterday?
>
Yes that fixed the issue for me. Thanks Eric.
Regards
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2010-04-03 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 6:03 2.6.34-rc3: Badness at kernel/lockdep.c:2706 Sachin Sant
2010-04-02 6:03 ` Sachin Sant
2010-04-02 14:28 ` Peter Zijlstra
2010-04-02 14:28 ` Peter Zijlstra
2010-04-02 14:59 ` Eric W. Biederman
2010-04-02 14:59 ` Eric W. Biederman
2010-04-03 8:34 ` Sachin Sant [this message]
2010-04-03 8:34 ` Sachin Sant
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=4BB6FDA1.3070502@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=peterz@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.