From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Christoph Lameter <cl@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the percpu tree
Date: Thu, 6 Jan 2011 15:18:15 +1100 [thread overview]
Message-ID: <20110106151815.9e5c2a1e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20110104051314.GA6748@mtj.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hi Tejun,
On Tue, 4 Jan 2011 06:13:14 +0100 Tejun Heo <tj@kernel.org> wrote:
>
> On Tue, Jan 04, 2011 at 03:21:05PM +1100, Stephen Rothwell wrote:
> > After merging the percpu tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > arch/x86/kernel/cpu/mcheck/therm_throt.c: In function 'intel_thermal_interrupt':
> > arch/x86/kernel/cpu/mcheck/therm_throt.c:368: error: implicit declaration of function 'this_cpu_has'
> >
> > Caused by commit 6ac0bb7148b93fb40bccba5dff06d51a3e3ea283 ("x86: use
> > this_cpu_has for thermal_interrupt").
> >
> > this_cpu_has() does not exist anywhere except in this introduced usage.
> >
> > I have used the percpu tree from next-20101231 for today.
>
> My apologies. I forgot an earlier patch to introduce this_cpu_has()
> macro. I've reverted the offending commit.
But that revert is not in your published for-next branch yet. I have
manually reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-01-06 4:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 4:21 linux-next: build failure after merge of the percpu tree Stephen Rothwell
2011-01-04 5:13 ` Tejun Heo
2011-01-06 4:18 ` Stephen Rothwell [this message]
2011-01-06 5:11 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 6:14 Stephen Rothwell
2023-12-11 8:31 ` Alexandre Ghiti
2023-12-11 19:25 ` Dennis Zhou
2018-02-26 3:57 Stephen Rothwell
2014-08-27 4:22 Stephen Rothwell
2010-09-10 2:45 Stephen Rothwell
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=20110106151815.9e5c2a1e.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.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