public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: MSM PMU Support in Commit ee3c454b
Date: Fri, 07 May 2010 10:12:39 -0700	[thread overview]
Message-ID: <1273252359.3542.21.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <000101caee07$104acdc0$30e06940$@deacon@arm.com>

On Fri, 2010-05-07 at 18:02 +0100, Will Deacon wrote:
> Hi Russell,
> 
> Commit ee3c454b `arm: msm: add oprofile pmu support' in your devel
> branch adds an IRQ to the static list in kernel/pmu.c. Patch 6064/1 in
> the patch system replaces this old functionality with runtime registration
> using a platform device, so this commit prevents that patch applying.
> The OProfile patches in the system also depend on the runtime registration
> patch, so they will become blocked too.

Oh, sorry about that. I didn't realize a change like that was pending.
When are you planning to merge these changes?

> I can update the patch in the patch system so it applies cleanly, but
> the mach-msm bsp will need updating to register the IRQ using the new
> mechanism. Daniel: would you like me to submit a patch to do this, or
> would you rather do it [since I'm unfamiliar with the mach]?

Either, but your more motivated as it's blocking your progress ..

Daniel

  reply	other threads:[~2010-05-07 17:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 17:02 MSM PMU Support in Commit ee3c454b Will Deacon
2010-05-07 17:12 ` Daniel Walker [this message]
2010-05-07 18:03   ` Russell King - ARM Linux
2010-05-07 18:04   ` Will Deacon
2010-05-07 18:16     ` Russell King - ARM Linux
2010-05-07 18:15 ` Russell King - ARM Linux
2010-05-07 18:24   ` Daniel Walker
2010-05-07 18:26     ` Russell King - ARM Linux
2010-05-07 18:59       ` Daniel Walker
2010-05-07 19:01         ` Russell King - ARM Linux
2010-05-07 19:20           ` Daniel Walker
2010-05-09  9:33   ` 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=1273252359.3542.21.camel@c-dwalke-linux.qualcomm.com \
    --to=dwalker@codeaurora.org \
    --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