linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: hw_breakpoint: fixes and improvements
Date: Sat, 27 Nov 2010 21:12:11 +0000	[thread overview]
Message-ID: <1290892331.30176.4.camel@jazzbox> (raw)
In-Reply-To: <20101127123939.GA5998@n2100.arm.linux.org.uk>

Hi Russell,

On Sat, 2010-11-27 at 12:39 +0000, Russell King - ARM Linux wrote:
> On Thu, Nov 25, 2010 at 05:08:15PM +0000, Will Deacon wrote:
> > All feedback welcome!
> 
> While in the subject of fixes, sparse seems to have a problem with
> hw_breakpoint's usage of percpu stuff:
> 
[...]

This appears to be because I access something declared as perf_event *[]
using something of type perf_event **. I plan on re-rolling these fixes
anyway as I found a problem with CONFIG_PREEMPT, so I'll add the
necessary casts to silence sparse to the series.

> perf_event.c seems to also have problems too:
> 
I don't think you've pulled my perf-split branch yet, so if you hold
fire on that I'll add some fixes to get rid of these warnings [I think I
noticed one of the issues before] and send another pull request in the
week.

Thanks!

Will

      reply	other threads:[~2010-11-27 21:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 17:08 [PATCH 0/4] ARM: hw_breakpoint: fixes and improvements Will Deacon
2010-11-25 17:08 ` [PATCH 1/4] ARM: hw_breakpoint: ensure OS lock is clear before writing to debug registers Will Deacon
2010-11-25 17:08 ` [PATCH 2/4] ARM: hw_breakpoint: reset control registers in hotplug path Will Deacon
2010-11-25 17:08 ` [PATCH 3/4] ARM: hw_breakpoint: correct and simplify alignment fixup code Will Deacon
2010-11-25 17:08 ` [PATCH 4/4] ARM: ptrace: fix style issue with hw_breakpoint interface Will Deacon
2010-11-27 12:39 ` [PATCH 0/4] ARM: hw_breakpoint: fixes and improvements Russell King - ARM Linux
2010-11-27 21:12   ` 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=1290892331.30176.4.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).