From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/2] arm64: hw_breakpoint: convert CPU hotplug notifier to new infrastructure
Date: Wed, 31 Aug 2016 17:50:03 +0100 [thread overview]
Message-ID: <20160831165002.GH29505@arm.com> (raw)
In-Reply-To: <20160831160427.5nilur7ky3rxn2by@linutronix.de>
On Wed, Aug 31, 2016 at 06:04:28PM +0200, Sebastian Andrzej Siewior wrote:
> On 2016-08-26 12:41:41 [+0100], Will Deacon wrote:
> >
> > It probably should be there anyway, since the current code is explicitly
> > disabling interrupts to mitigate being called with them enabled and debug
> > is something we want as early as possible.
>
> Good. This will go via the ARM64 tree then?
Yup, I can queue these two for 4.9 if you're happy enough with them.
Will
next prev parent reply other threads:[~2016-08-31 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 10:35 [RFC PATCH 1/2] arm64: hw_breakpoint: convert CPU hotplug notifier to new infrastructure Will Deacon
2016-08-26 10:35 ` [RFC PATCH 2/2] arm64: debug: convert OS lock " Will Deacon
2016-08-26 11:28 ` [RFC PATCH 1/2] arm64: hw_breakpoint: convert " Sebastian Andrzej Siewior
2016-08-26 11:41 ` Will Deacon
2016-08-31 16:04 ` Sebastian Andrzej Siewior
2016-08-31 16:50 ` Will Deacon [this message]
2016-08-31 15:35 ` Lorenzo Pieralisi
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=20160831165002.GH29505@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).