From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM perf events spin locks
Date: Tue, 30 Nov 2010 14:46:30 -0000 [thread overview]
Message-ID: <004801cb909d$6010f3a0$2032dae0$@deacon@arm.com> (raw)
In-Reply-To: <20101130143141.GA2377@n2100.arm.linux.org.uk>
> > I don't mind doing it as a separate patch after Russell has pulled my
> > perf-split branch.
>
> You mean this?
>
> commit f1690d17d2c7afa2a2079e3c91eb2bca8c1c5ecd
> Merge: 612275a 43eab87
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> Date: Fri Nov 26 10:26:43 2010 +0000
>
> Merge branch 'perf-split' of git://linux-arm.org/linux-2.6-wd into devel-stable
Aha, brilliant - thanks.
> Sorry, I didn't push the tree out for a week or so because I was busy with
> other things (like the pgtable stuff.)
There's no rest for the weary! I'll submit the patch to fix perf for sparse
to the patch system (I didn't realise you'd pulled my changes on Friday) and
tackle this spinlock thing at the same time.
Cheers,
Will
prev parent reply other threads:[~2010-11-30 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 10:08 ARM perf events spin locks Jamie Iles
2010-11-30 10:41 ` Will Deacon
2010-11-30 10:58 ` Jamie Iles
2010-11-30 13:49 ` Will Deacon
2010-11-30 13:54 ` Jamie Iles
2010-11-30 13:59 ` Will Deacon
2010-11-30 14:31 ` Russell King - ARM Linux
2010-11-30 14:46 ` Will Deacon [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='004801cb909d$6010f3a0$2032dae0$@deacon@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).