From: Mathias Krause <minipli@googlemail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Mathias Krause <minipli@googlemail.com>
Subject: [PATCH 0/5] x86: __ref / __refdata cleanup
Date: Sun, 19 Jul 2015 18:22:49 +0200 [thread overview]
Message-ID: <1437322974-11081-1-git-send-email-minipli@googlemail.com> (raw)
This series drops quite a few -- relatively speaking -- __ref /
__refdata annotations in the x86 code. They used to be needed in
__cpuinit times but those are long gone. Now those annotations may
only serve as an additional error source, hiding legitimate section
mismatches. So we better get rid of them.
Please apply.
Mathias Krause (5):
x86, ACPI: Get rid of the acpi_map_cpu() wrapper
x86, apic: Drop bogus __refdata annotation of cpu notifier
x86, cpuid: Drop bogus __refdata annotation of cpu notifier
x86, smpboot: Drop bogus __ref annotation from remove_cpu_from_maps()
x86, topology: Drop bogus __ref annotations
arch/x86/kernel/acpi/boot.c | 8 +-------
arch/x86/kernel/apic/x2apic_cluster.c | 2 +-
arch/x86/kernel/cpuid.c | 2 +-
arch/x86/kernel/smpboot.c | 2 +-
arch/x86/kernel/topology.c | 4 ++--
5 files changed, 6 insertions(+), 12 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-07-19 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 16:22 Mathias Krause [this message]
2015-07-19 16:22 ` [PATCH 1/5] x86, ACPI: Get rid of the acpi_map_cpu() wrapper Mathias Krause
2015-07-19 16:22 ` [PATCH 2/5] x86, apic: Drop bogus __refdata annotation of cpu notifier Mathias Krause
2015-07-19 16:22 ` [PATCH 3/5] x86, cpuid: " Mathias Krause
2015-07-19 16:22 ` [PATCH 4/5] x86, smpboot: Drop bogus __ref annotation from remove_cpu_from_maps() Mathias Krause
2015-07-19 16:22 ` [PATCH 5/5] x86, topology: Drop bogus __ref annotations Mathias Krause
2015-07-20 7:39 ` [PATCH 0/5] x86: __ref / __refdata cleanup Ingo Molnar
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=1437322974-11081-1-git-send-email-minipli@googlemail.com \
--to=minipli@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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).