From: jamie.iles@picochip.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch/arm: Fix missing define for ARM_PMU_DEVICE_CPU
Date: Thu, 29 Apr 2010 09:12:18 +0100 [thread overview]
Message-ID: <20100429081218.GA14783@wear.picochip.com> (raw)
In-Reply-To: <201004290231.03440.PeterHuewe@gmx.de>
On Thu, Apr 29, 2010 at 02:31:03AM +0200, Peter Huewe wrote:
> From: Peter Huewe <peterhuewe@gmx.de>
>
> This patch adds a define for ARM_PMU_DEVICE_CPU which seemed to be
> missing/undefined and caused some build failures [1-4].
>
> I defined ARM_PMU_DEVICE_CPU = -1 as stated in
> Documentation/driver_model/platform.txt to indicate there is only one.
> I'm _not_ sure if this is correct, but due to the static nature of the
> define I assume it is.
Hi Peter,
This build error is due to the core patch of Will's "ARM: pmu: provide a
registration mechanism for IRQs" patch series not being merged yet. I'm not
sure what the status of that patch is at the moment though.
Jamie
next prev parent reply other threads:[~2010-04-29 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 0:31 [PATCH] arch/arm: Fix missing define for ARM_PMU_DEVICE_CPU Peter Huewe
2010-04-29 8:12 ` Jamie Iles [this message]
2010-04-29 8:26 ` Will Deacon
2010-04-29 10:18 ` Peter Hüwe
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=20100429081218.GA14783@wear.picochip.com \
--to=jamie.iles@picochip.com \
--cc=linux-arm-kernel@lists.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