From: PeterHuewe@gmx.de (Peter Hüwe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch/arm: Fix missing define for ARM_PMU_DEVICE_CPU
Date: Thu, 29 Apr 2010 12:18:46 +0200 [thread overview]
Message-ID: <201004291218.46341.PeterHuewe@gmx.de> (raw)
In-Reply-To: <1272529580.24662.10.camel@e102144-lin.cambridge.arm.com>
Am Donnerstag 29 April 2010 10:26:20 schrieb Will Deacon:
> > 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 submitted the series to Russell's patch system on 9 April.
> However, as you know, he's currently without an internet connection and
> the patch system has gone offline.
Ah, didn't know about this - then sorry to 'bug' you with my patch :)
> Peter: if you're interested, the patch series I sent to the ARM
> Linux list is archived here:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2010-March/012113.html
Thanks for the Link - I'll have a look at it.
Thanks,
Peter
prev parent reply other threads:[~2010-04-29 10:18 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
2010-04-29 8:26 ` Will Deacon
2010-04-29 10:18 ` Peter Hüwe [this message]
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=201004291218.46341.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--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