From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v4 3/3] arm: omap4: support pmu
Date: Sun, 15 May 2011 15:16:00 +0100 [thread overview]
Message-ID: <1305468960.2848.2.camel@jazzbox> (raw)
In-Reply-To: <BANLkTimkrf8-+-JTQy-gWK9t9grj-n0Ftw@mail.gmail.com>
[Adding Avik],
On Sat, 2011-05-14 at 09:48 +0100, Ming Lei wrote:
> Hi Rabin,
>
> 2011/5/14 Rabin Vincent <rabin@rab.in>:
> > What happened to this patch? It is neither in mainline nor in
> > linux-next.
> >
>
> This patch depends on the two with titles:
>
> introduce cross trigger interface helpers
> pmu: allow platform specific irq enable/disable handling
>
> and the above patches have been submitted to RMK's patch system
> as 6839/1 and 6840/1, but not been pushed to -next or mainline by rmk,
> so I can't ask omap guys to merge this one into their tree now.
I don't think that Avik's problem with this patch has been fully
addressed yet:
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-April/046899.html
So regardless of the state of -next, I think there's still some more
work to do on this code before it can go upstream.
Will
next prev parent reply other threads:[~2011-05-15 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:38 [patch v4 0/3] arm: pmu: support pmu/perf on OMAP4 tom.leiming at gmail.com
2011-03-08 15:38 ` [patch v4 1/3] arm: introduce cross trigger interface helpers tom.leiming at gmail.com
2011-03-08 16:31 ` Ben Dooks
2011-03-24 14:41 ` Ming Lei
2011-03-09 5:38 ` Santosh Shilimkar
2011-03-08 15:38 ` [patch v4 2/3] arm: pmu: allow platform specific irq enable/disable handling tom.leiming at gmail.com
2011-03-08 15:38 ` [patch v4 3/3] arm: omap4: support pmu tom.leiming at gmail.com
2011-05-14 8:18 ` Rabin Vincent
2011-05-14 8:48 ` Ming Lei
2011-05-14 9:49 ` Russell King - ARM Linux
2011-05-15 14:16 ` Will Deacon [this message]
2011-05-16 1:28 ` Ming Lei
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=1305468960.2848.2.camel@jazzbox \
--to=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).