From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ARM: pmu: provide a registration mechanism for IRQs [v3]
Date: Thu, 29 Apr 2010 17:05:40 +0100 [thread overview]
Message-ID: <20100429160540.GE4877@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <000501cae7b5$97a76fb0$c6f64f10$@deacon@arm.com>
On Thu, Apr 29, 2010 at 05:04:04PM +0100, Will Deacon wrote:
> Hi Russell,
>
> > Please can we have an ordered set which doesn't break compilation.
> > What I think should happen is the first patch should introduce the
> > new definitions required for the platform data, and the rest of the
> > first patch should come at the very end.
>
> Sorry about this. I've split up the first patch so that the first
> half is now:
>
>
> ARM: pmu: add enum describing PMU types
>
> This patch adds an enum describing the potential PMU device types in
> preparation for PMU device registration via platform devices.
>
> diff --git a/arch/arm/include/asm/pmu.h b/arch/arm/include/asm/pmu.h
> index 2829b9f..44bec1f 100644
> --- a/arch/arm/include/asm/pmu.h
> +++ b/arch/arm/include/asm/pmu.h
> @@ -12,6 +12,11 @@
> #ifndef __ARM_PMU_H__
> #define __ARM_PMU_H__
>
> +enum arm_pmu_type {
> + ARM_PMU_DEVICE_CPU = 0,
> + ARM_NUM_PMU_DEVICES,
> +};
> +
> #ifdef CONFIG_CPU_HAS_PMU
>
> struct pmu_irqs {
>
>
> which gets rid of the compilation failures. I can either supersede
> the existing patch with two more or resubmit the whole series. Which
> would you prefer?
Can you just deal with the single patch to be superseded; the rest are
fine.
next prev parent reply other threads:[~2010-04-29 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 15:16 [PATCH 0/6] ARM: pmu: provide a registration mechanism for IRQs [v3] Will Deacon
2010-03-25 15:16 ` [PATCH 1/6] ARM: pmu: register IRQs at runtime Will Deacon
2010-03-25 15:16 ` [PATCH 2/6] ARM: Realview: register PMU IRQs during board initialisation Will Deacon
2010-03-25 15:16 ` [PATCH 3/6] ARM: OMAP: " Will Deacon
2010-03-25 15:16 ` [PATCH 4/6] ARM: BCMRING: register PMU IRQ " Will Deacon
2010-03-25 15:16 ` [PATCH 5/6] ARM: iop3xx: register PMU IRQs " Will Deacon
2010-03-25 15:16 ` [PATCH 6/6] ARM: pxa: " Will Deacon
2010-03-25 17:35 ` [PATCH 4/6] ARM: BCMRING: register PMU IRQ " Leo (Hao) Chen
2010-03-25 15:36 ` [PATCH 1/6] ARM: pmu: register IRQs at runtime Jamie Iles
2010-04-28 21:36 ` [PATCH 0/6] ARM: pmu: provide a registration mechanism for IRQs [v3] Russell King - ARM Linux
2010-04-29 16:04 ` Will Deacon
2010-04-29 16:05 ` Russell King - ARM Linux [this message]
2010-04-29 16:15 ` Will Deacon
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=20100429160540.GE4877@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).