linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linuxppc-dev@ozlabs.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bugme-daemon@bugzilla.kernel.org,
	Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: [Bug 10714] Badness seen on 2.6.26-rc2 with lockdep enabled
Date: Sun, 15 Jun 2008 09:29:21 +1000	[thread overview]
Message-ID: <1213486161.8129.89.camel@pasglop> (raw)
In-Reply-To: <20080614230424.GA21168@cs181133002.pp.htv.fi>

On Sun, 2008-06-15 at 02:04 +0300, Adrian Bunk wrote:
> On Sat, Jun 14, 2008 at 10:12:02PM +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.25.  Please verify if it still should be listed.
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10714
> > Subject		: Badness seen on 2.6.26-rc2 with lockdep enabled
> > Submitter	: Balbir Singh <balbir@linux.vnet.ibm.com>
> > Date		: 2008-05-14 12:57 (32 days old)
> > References	: http://marc.info/?l=linux-kernel&m=121076917429133&w=4
> 
> Benjamin, you said you wanted to have a look at this?

Ah yes, slipped out of my mind. It's probably a missing annotation in
the RTAS code, I'll have a look tomorrow.

Thanks,
Ben.

      reply	other threads:[~2008-06-14 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RzbtSgMztjP.A.R0C.dIDVIB@albercik>
     [not found] ` <Jn7irxIunJK.A.ggF.4KDVIB@albercik>
2008-06-14 23:04   ` [Bug 10714] Badness seen on 2.6.26-rc2 with lockdep enabled Adrian Bunk
2008-06-14 23:29     ` Benjamin Herrenschmidt [this message]

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=1213486161.8129.89.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=rjw@sisk.pl \
    /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).