From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: powerpc allmodconfig build broken due to commit 15863ff3b (powerpc: Make chip-id information available to userspace)
Date: Sun, 08 Sep 2013 17:28:46 -0700 [thread overview]
Message-ID: <522D163E.80106@roeck-us.net> (raw)
Hi all,
powerpc allmodconfig build on the latest upstream kernel results in:
ERROR: ".cpu_to_chip_id" [drivers/block/mtip32xx/mtip32xx.ko] undefined!
This is due to commit 15863ff3b (powerpc: Make chip-id information available to userspace).
Not surprising, as cpu_to_chip_id() is not exported.
Reverting this commit fixes the problem. Any good idea how to fix it for real ?
Guenter
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: powerpc allmodconfig build broken due to commit 15863ff3b (powerpc: Make chip-id information available to userspace)
Date: Sun, 08 Sep 2013 17:28:46 -0700 [thread overview]
Message-ID: <522D163E.80106@roeck-us.net> (raw)
Hi all,
powerpc allmodconfig build on the latest upstream kernel results in:
ERROR: ".cpu_to_chip_id" [drivers/block/mtip32xx/mtip32xx.ko] undefined!
This is due to commit 15863ff3b (powerpc: Make chip-id information available to userspace).
Not surprising, as cpu_to_chip_id() is not exported.
Reverting this commit fixes the problem. Any good idea how to fix it for real ?
Guenter
next reply other threads:[~2013-09-09 0:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 0:28 Guenter Roeck [this message]
2013-09-09 0:28 ` powerpc allmodconfig build broken due to commit 15863ff3b (powerpc: Make chip-id information available to userspace) Guenter Roeck
2013-09-09 23:55 ` Asai Thambi S P
2013-09-09 23:55 ` Asai Thambi S P
2013-09-10 1:18 ` Guenter Roeck
2013-09-10 1:18 ` Guenter Roeck
2013-09-10 22:02 ` Benjamin Herrenschmidt
2013-09-10 22:02 ` Benjamin Herrenschmidt
2013-09-10 22:50 ` Guenter Roeck
2013-09-10 22:50 ` Guenter Roeck
2013-09-11 6:36 ` Vasant Hegde
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=522D163E.80106@roeck-us.net \
--to=linux@roeck-us.net \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sbhat@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.