From: Will Deacon <will.deacon@arm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/2] ARM: shmobile: enable PMU(Performance Monitoring Unit)
Date: Fri, 07 Sep 2012 08:46:56 +0000 [thread overview]
Message-ID: <20120907084656.GB15916@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <504952F7.6090906@kmckk.co.jp>
On Fri, Sep 07, 2012 at 02:50:47AM +0100, Tetsuyuki Kobayashi wrote:
> (2012/09/06 20:21), Will Deacon wrote:
> > On Thu, Sep 06, 2012 at 12:14:05PM +0100, Tetsuyuki Kobayshi wrote:
> >> From: Tetsuyuki Kobayashi <koba@kmckk.co.jp>
> > Actually, it's better if you just base your branch against that one when you
> > send it to arm-soc for merging. That way, other SoCs can also develop
> > against that branch without having to worry about each other.
> >
> I see.
> I thought that removing ARM_PMU_DEVICE_CPU depends on your pmu/cleanup
> branch, but I found it does not.
It will probably build alright for you without my patches, but I don't
thinkt it will work correctly as we'll fail to reserve the PMU.
Will
next prev parent reply other threads:[~2012-09-07 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 2:48 [PATCH 0/2] ARM: shmobile: enable PMU(Performance Monitoring Unit) Tetsuyuki Kobayshi
2012-09-06 5:30 ` [PATCH v2 " Tetsuyuki Kobayshi
2012-09-06 5:30 ` [PATCH v2 1/2] ARM: shmobile: sh73a0: " Tetsuyuki Kobayshi
2012-09-06 9:11 ` Will Deacon
2012-09-06 9:57 ` Tetsuyuki Kobayashi
2012-09-06 11:14 ` [PATCH v3 0/2] ARM: shmobile: " Tetsuyuki Kobayshi
2012-09-06 11:14 ` [PATCH v3 1/2] ARM: shmobile: sh73a0: " Tetsuyuki Kobayshi
2012-09-06 11:14 ` [PATCH v3 2/2] ARM: shmobile: emev2: " Tetsuyuki Kobayshi
2012-09-06 11:21 ` [PATCH v3 0/2] ARM: shmobile: " Will Deacon
2012-09-07 1:50 ` Tetsuyuki Kobayashi
2012-09-07 8:46 ` Will Deacon [this message]
2012-09-07 13:25 ` Simon Horman
2012-09-11 8:10 ` Simon Horman
2012-09-06 5:30 ` [PATCH v2 2/2] ARM: shmobile: emev2: " Tetsuyuki Kobayshi
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=20120907084656.GB15916@mudshark.cambridge.arm.com \
--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).