From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: hw_breakpoint: Do not use __cpuinitdata for dbg_cpu_pm_nb
Date: Wed, 10 Apr 2013 13:04:30 +0000 [thread overview]
Message-ID: <5165635E.50804@arm.com> (raw)
In-Reply-To: <20130410125316.GC26992@mudshark.cambridge.arm.com>
On 10/04/13 13:53, Will Deacon wrote:
> On Wed, Apr 10, 2013 at 01:11:16PM +0100, Bastian Hecht wrote:
>>> Will, we have the same issue in arch/arm/kernel/perf_event_cpu.c.
>>> Lorenzo is currently working on an appropriate patch.
>
> I don't think we do. The __cpuinitdata annotation there is only used on a
> hotplug notifier, which should be fine.
You right, I got confused about what is already upstream.
-- Dietmar
>
> Will
>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
WARNING: multiple messages have this Message-ID (diff)
From: dietmar.eggemann@arm.com (Dietmar Eggemann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: hw_breakpoint: Do not use __cpuinitdata for dbg_cpu_pm_nb
Date: Wed, 10 Apr 2013 14:04:30 +0100 [thread overview]
Message-ID: <5165635E.50804@arm.com> (raw)
In-Reply-To: <20130410125316.GC26992@mudshark.cambridge.arm.com>
On 10/04/13 13:53, Will Deacon wrote:
> On Wed, Apr 10, 2013 at 01:11:16PM +0100, Bastian Hecht wrote:
>>> Will, we have the same issue in arch/arm/kernel/perf_event_cpu.c.
>>> Lorenzo is currently working on an appropriate patch.
>
> I don't think we do. The __cpuinitdata annotation there is only used on a
> hotplug notifier, which should be fine.
You right, I got confused about what is already upstream.
-- Dietmar
>
> Will
>
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2013-04-10 13:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 10:04 [PATCH] ARM: hw_breakpoint: Do not use __cpuinitdata for dbg_cpu_pm_nb Bastian Hecht
2013-04-10 10:04 ` Bastian Hecht
2013-04-10 11:11 ` Will Deacon
2013-04-10 11:11 ` Will Deacon
2013-04-10 11:26 ` Bastian Hecht
2013-04-10 11:26 ` Bastian Hecht
2013-04-10 12:04 ` Dietmar Eggemann
2013-04-10 12:04 ` Dietmar Eggemann
2013-04-10 12:11 ` Bastian Hecht
2013-04-10 12:11 ` Bastian Hecht
2013-04-10 12:53 ` Will Deacon
2013-04-10 12:53 ` Will Deacon
2013-04-10 13:04 ` Dietmar Eggemann [this message]
2013-04-10 13:04 ` Dietmar Eggemann
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=5165635E.50804@arm.com \
--to=dietmar.eggemann@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.