public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] lockdep updates
Date: Mon, 3 May 2010 15:00:35 +0200	[thread overview]
Message-ID: <20100503130035.GA19763@elte.hu> (raw)
In-Reply-To: <20100503072331.GD6642@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > Ingo,
> > 
> > Please pull the core/locking branch that can be found at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > 	core/locking
> > 
> > Note there is also a merge of v2.6.34-rc6 because these patches
> > depend on older per cpu updates.
> > 
> > Thanks,
> > 	Frederic
> > ---
> > 
> > Frederic Weisbecker (2):
> >       lockdep: Fix redundant_hardirqs_on incremented with irqs enabled
> >       lockdep: Simplify debug atomic ops
> > 
> > 
> >  kernel/lockdep.c           |    7 ++++++-
> >  kernel/lockdep_internals.h |   10 ++--------
> >  2 files changed, 8 insertions(+), 9 deletions(-)

this one is causing:

kernel/lockdep.c:2306: error: 'lockdep_stats' undeclared (first use in this function)
kernel/lockdep.c:2306: error: (Each undeclared identifier is reported only once
kernel/lockdep.c:2306: error: for each function it appears in.)

with these settings:

CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_LOCKDEP is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set

Thanks,

	Ingo

  reply	other threads:[~2010-05-03 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 17:34 [GIT PULL] lockdep updates Frederic Weisbecker
2010-05-03  7:23 ` Ingo Molnar
2010-05-03 13:00   ` Ingo Molnar [this message]
2010-05-03 13:47     ` Frederic Weisbecker
  -- strict thread matches above, loose matches on Subject: below --
2008-02-25 22:17 Peter Zijlstra
2008-01-16  9:28 Peter Zijlstra

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=20100503130035.GA19763@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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