public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	fweisbec@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org
Subject: Re: [PATCH v2] x86, nmi_watchdog:  Remove ARCH_HAS_NMI_WATCHDOG and rely on CONFIG_HARDLOCKUP_DETECTOR
Date: Wed, 22 Dec 2010 14:01:08 -0500	[thread overview]
Message-ID: <20101222190108.GE3743@redhat.com> (raw)
In-Reply-To: <20101222162452.GA23665@elte.hu>

On Wed, Dec 22, 2010 at 05:24:52PM +0100, Ingo Molnar wrote:
> 
> * Don Zickus <dzickus@redhat.com> wrote:
> 
> > Tested with
> > ARCH=i386: allnoconfig, defconfig, allyesconfig, (various broken configs)
> > ARCH=x86_64: allnoconfig, defconfig, allyesconfig, (various broken configs)
> > 
> > Hopefully, after this patch I won't get any more compile broken emails. :-)
> > 
> > Signed-off-by: Don Zickus <dzickus@redhat.com>
> 
> There's still some assumptions in the oprofile code, which breaks the build with 
> your patch applied:
> 
>  arch/x86/oprofile/op_model_p4.c:394:4: error: implicit declaration of function ‘release_perfctr_nmi’
>  arch/x86/oprofile/op_model_p4.c:403:4: error: implicit declaration of function ‘release_evntsel_nmi’
>  arch/x86/oprofile/op_model_p4.c:419:3: error: implicit declaration of function ‘reserve_perfctr_nmi’
>  arch/x86/oprofile/op_model_p4.c:428:3: error: implicit declaration of function ‘reserve_evntsel_nmi’
> 
> Config attached.

Thanks.  I sent a patch to fix this.  Basically they were using
linux/nmi.h instead of asm/nmi.h.

Cheers,
Don

      reply	other threads:[~2010-12-22 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 14:25 [PATCH v2] x86, nmi_watchdog: Remove ARCH_HAS_NMI_WATCHDOG and rely on CONFIG_HARDLOCKUP_DETECTOR Don Zickus
2010-12-22 16:24 ` Ingo Molnar
2010-12-22 19:01   ` Don Zickus [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=20101222190108.GE3743@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox