public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: ink@jurassic.park.msu.ru, tj@kernel.org, max@stro.at,
	linux-kernel@vger.kernel.org, dhowells@redhat.com
Subject: Re: >= 2.6.30 broken alpha smp build
Date: Fri, 26 Jun 2009 12:21:52 -0700	[thread overview]
Message-ID: <20090626122152.e124254b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090626115746.09314757.akpm@linux-foundation.org>

On Fri, 26 Jun 2009 11:57:46 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> Anyway, we need a backportable fix, so I'll put this through
> some build testing:

The allmodconfig build has more problems:

ERROR: "per_cpu__cookie_scratch" [net/ipv6/ipv6.ko] undefined!
ERROR: "per_cpu__rcu_torture_batch" [kernel/rcutorture.ko] undefined!
ERROR: "per_cpu__rcu_torture_count" [kernel/rcutorture.ko] undefined!
ERROR: "clk_enable" [drivers/i2c/busses/i2c-designware.ko] undefined!
ERROR: "clk_get" [drivers/i2c/busses/i2c-designware.ko] undefined!
ERROR: "clk_put" [drivers/i2c/busses/i2c-designware.ko] undefined!
ERROR: "clk_disable" [drivers/i2c/busses/i2c-designware.ko] undefined!
ERROR: "clk_get_rate" [drivers/i2c/busses/i2c-designware.ko] undefined!
ERROR: "per_cpu__msg_schedule" [crypto/sha512_generic.ko] undefined!
ERROR: "per_cpu__ioc_count" [block/cfq-iosched.ko] undefined!
ERROR: "per_cpu__ioc_count" [block/as-iosched.ko] undefined!

It looks like making these DEFINE_PER_CPUs non-static will fix it up. 
What's that all about?


  reply	other threads:[~2009-06-26 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  9:08 >= 2.6.30 broken alpha smp build maximilian attems
2009-06-25 18:54 ` Andrew Morton
2009-06-26  0:43   ` Tejun Heo
2009-06-26 12:47     ` Ivan Kokshaysky
2009-06-26 18:57       ` Andrew Morton
2009-06-26 19:21         ` Andrew Morton [this message]
2009-06-28  0:49           ` [PATCH] alpha: fix percpu build breakage Tejun Heo
2009-06-28 11:39             ` Ivan Kokshaysky
2009-06-28 12:21               ` Tejun Heo
2009-06-28 15:50                 ` Ivan Kokshaysky

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=20090626122152.e124254b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    --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