linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM perf updates for 4.1
Date: Mon, 13 Apr 2015 11:30:22 +0200	[thread overview]
Message-ID: <CAMuHMdUPpAnJz7Pv=aTv+ZhCkjDPLkry_gV6=GFMmSCEsXEOSw@mail.gmail.com> (raw)
In-Reply-To: <20150413091011.GA1582@arm.com>

Hi Will,

On Mon, Apr 13, 2015 at 11:10 AM, Will Deacon <will.deacon@arm.com> wrote:
> On Tue, Apr 07, 2015 at 04:05:40PM +0100, Geert Uytterhoeven wrote:
>> On Fri, Mar 27, 2015 at 6:22 PM, Will Deacon <will.deacon@arm.com> wrote:
>> > Will Deacon (1):
>> >       ARM: pmu: add support for interrupt-affinity property
>>
>> As most DTSes lack this property, we now get scary warnings:
>>
>>         CPU PMU: Failed to parse <no-node>/interrupt-affinity[0]
>
> That's a harmless warning (i.e. perf will `work' as before), but I'd like to
> print something to say that we didn't find the property.
>
>> BTW, shouldn't the DT update go in first, or together with the code update?
>
> It's going via the arm64 tree (I had to choose one of the trees for the
> binding, since they both arm and arm64 use it).

OK. Will start to pull arm64 too into renesas-drivers...

BTW, time to start unifying arm32 and arm64? ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2015-04-13  9:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 17:22 [GIT PULL] ARM perf updates for 4.1 Will Deacon
2015-04-07 15:05 ` Geert Uytterhoeven
2015-04-13  9:10   ` Will Deacon
2015-04-13  9:28     ` Maxime Ripard
2015-04-13 10:21       ` Will Deacon
2015-04-13  9:30     ` Geert Uytterhoeven [this message]
2015-04-13  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='CAMuHMdUPpAnJz7Pv=aTv+ZhCkjDPLkry_gV6=GFMmSCEsXEOSw@mail.gmail.com' \
    --to=geert@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).