From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Don Zickus <dzickus@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] Lockup detector build fixes
Date: Sun, 16 May 2010 04:36:49 +0200 [thread overview]
Message-ID: <20100516023648.GD7645@nowhere> (raw)
In-Reply-To: <1273977240-30800-1-git-send-regression-fweisbec@gmail.com>
On Sun, May 16, 2010 at 04:33:56AM +0200, Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the perf/nmi branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> perf/nmi
>
> Thanks,
> Frederic
Tested on x86 and Sparc 64 with and without CONFIG_LOCKUP_DETECTOR.
No problem so far. Tell me if you find any.
next prev parent reply other threads:[~2010-05-16 2:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 5:53 linux-next: build failure after merge of the final tree Stephen Rothwell
2010-05-14 15:03 ` Don Zickus
2010-05-15 7:37 ` Ingo Molnar
2010-05-15 20:28 ` Frederic Weisbecker
2010-05-16 2:33 ` [GIT PULL] Lockup detector build fixes Frederic Weisbecker
2010-05-16 2:36 ` Frederic Weisbecker [this message]
2010-05-16 7:56 ` Ingo Molnar
2010-05-17 13:44 ` Don Zickus
2010-05-16 2:33 ` [PATCH 1/4] lockup_detector: Update some config Frederic Weisbecker
2010-05-16 2:33 ` [PATCH 2/4] lockup_detector: Adapt CONFIG_PERF_EVENT_NMI to other archs Frederic Weisbecker
2010-05-16 2:33 ` [PATCH 3/4] lockup_detector: Introduce CONFIG_HARDLOCKUP_DETECTOR Frederic Weisbecker
2010-05-16 2:34 ` [PATCH 4/4] lockup_detector: Cross arch compile fixes Frederic Weisbecker
2010-05-14 15:11 ` linux-next: build failure after merge of the final tree Don Zickus
2010-05-16 9:20 ` [tip:perf/nmi] lockup_detector: Cross arch compile fixes tip-bot for Don Zickus
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=20100516023648.GD7645@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dzickus@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).