From: Mike Frysinger <vapier@gentoo.org>
To: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Cc: uclinux-dist-devel@blackfin.uclinux.org
Subject: [PATCH 2/2] Blackfin: use new common PERCPU_INPUT define
Date: Thu, 31 Mar 2011 15:52:02 -0400 [thread overview]
Message-ID: <1301601122-25431-2-git-send-email-vapier@gentoo.org> (raw)
In-Reply-To: <1301601122-25431-1-git-send-email-vapier@gentoo.org>
The Blackfin percpu input sections are outdated, so rather than update
them, drop them completely and use the new common define.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
arch/blackfin/kernel/vmlinux.lds.S | 8 +-------
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/arch/blackfin/kernel/vmlinux.lds.S b/arch/blackfin/kernel/vmlinux.lds.S
index 0e38042..bc0bf76 100644
--- a/arch/blackfin/kernel/vmlinux.lds.S
+++ b/arch/blackfin/kernel/vmlinux.lds.S
@@ -155,14 +155,8 @@ SECTIONS
SECURITY_INITCALL
INIT_RAM_FS
- . = ALIGN(4);
___per_cpu_load = .;
- ___per_cpu_start = .;
- *(.data.percpu.first)
- *(.data.percpu.page_aligned)
- *(.data.percpu)
- *(.data.percpu.shared_aligned)
- ___per_cpu_end = .;
+ PERCPU_INPUT
EXIT_DATA
__einitdata = .;
--
1.7.4.1
next prev parent reply other threads:[~2011-03-31 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 19:52 [PATCH 1/2] percpu: unify input section names Mike Frysinger
2011-03-31 19:52 ` Mike Frysinger [this message]
2011-03-31 19:55 ` [uclinux-dist-devel] [PATCH 2/2] Blackfin: use new common PERCPU_INPUT define Mike Frysinger
2011-04-01 7:29 ` [PATCH 1/2] percpu: unify input section names Tejun Heo
2011-04-01 22:15 ` [PATCH 1/2 v2] " Mike Frysinger
2011-04-03 23:44 ` Tejun Heo
2011-05-24 1:46 ` [uclinux-dist-devel] " Mike Frysinger
2011-05-24 9:37 ` Tejun Heo
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=1301601122-25431-2-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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
all inboxes | Powered by JetHome®