From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
yinghai@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2008-10-02-16-17 uploaded
Date: Wed, 8 Oct 2008 11:50:24 +0200 [thread overview]
Message-ID: <20081008095024.GA31622@elte.hu> (raw)
In-Reply-To: <20081007170103.3dcb6384.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> > > could be merging problem again.
> > >
> > > please check in arch/x86/kernel/vmliux_64.lds.S
> > >
> > > it should be like
> > >
> > > __con_initcall_end = .;
> > > __x86_cpu_dev_start = .;
> > > .x86_cpu_dev.init : AT(ADDR(.x86_cpu_dev.init) - LOAD_OFFSET) {
> > > *(.x86_cpu_dev.init)
> > > }
> > > __x86_cpu_dev_end = .;
> > >
> > > DYN_ARRAY_INIT(8)
> > >
> > > SECURITY_INIT
>
> The above is what's presently in Ingo's "tip" tree.
>
> > Oh, yes. like this.
> > ==
> > __con_initcall_end = .;
> > __x86_cpu_dev_start = .;
> > .x86_cpu_dev.init : AT(ADDR(.x86_cpu_dev.init) - LOAD_OFFSET) {
> > *(.x86_cpu_dev.init)
> > }
> > SECURITY_INIT
> > __x86_cpu_dev_end = .;
> > ==
> >
> > I'll try next version when it comes.
>
> If that fixes it then Ingo's tree will need fixing too, I suppose.
it should be:
__x86_cpu_dev_end = .;
DYN_ARRAY_INIT(8)
SECURITY_INIT
and that's what it is in -tip. Am i missing something?
Ingo
prev parent reply other threads:[~2008-10-08 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810022318.m92NI14X031834@imap1.linux-foundation.org>
2008-10-03 0:17 ` Randy.Dunlap
2008-10-03 0:45 ` Andrew Morton
2008-10-03 3:32 ` Randy Dunlap
2008-10-03 3:37 ` Andrew Morton
2008-10-03 3:43 ` Randy Dunlap
2008-10-07 7:33 ` KAMEZAWA Hiroyuki
2008-10-07 16:18 ` Yinghai Lu
2008-10-07 23:47 ` KAMEZAWA Hiroyuki
2008-10-08 0:01 ` Andrew Morton
2008-10-08 0:34 ` KAMEZAWA Hiroyuki
2008-10-08 9:50 ` Ingo Molnar [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=20081008095024.GA31622@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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
Powered by JetHome