On Tue, Jun 12, 2007 at 10:50:33AM +0900, Yasunori Goto wrote:
> > >
> > > If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
> > > CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
> > > other disabled, you end up with a reference between __init and a regular
> > >
> >
> > If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
> > CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
> > other disabled, you end up with a reference between __init and a regular
> > non-init function.
>
> My plan is to define dedicated sections for both
>
> If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
> CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
> other disabled, you end up with a reference between __init and a regular
> non-init function.
My plan is to define dedicated sections for both __devinit and
On Mon, Jun 11, 2007 at 08:27:32AM -0700, Randy Dunlap wrote:
> On Mon, 11 Jun 2007 14:09:55 +0900 Paul Mundt wrote:
> > On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
> > > On Mon, 11 Jun 2007 13:35:43 +0900
> > > Paul Mundt <[EMAIL PROTECTED]> wrote:
> > > > This happens
On Mon, 11 Jun 2007 14:09:55 +0900 Paul Mundt wrote:
> On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
> > On Mon, 11 Jun 2007 13:35:43 +0900
> > Paul Mundt <[EMAIL PROTECTED]> wrote:
> >
> > > When building with memory hotplug enabled and cpu hotplug disabled, we
> > > end up
On Mon, 11 Jun 2007 14:09:55 +0900 Paul Mundt wrote:
On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt [EMAIL PROTECTED] wrote:
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the
On Mon, Jun 11, 2007 at 08:27:32AM -0700, Randy Dunlap wrote:
On Mon, 11 Jun 2007 14:09:55 +0900 Paul Mundt wrote:
On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt [EMAIL PROTECTED] wrote:
This happens because
If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
other disabled, you end up with a reference between __init and a regular
non-init function.
My plan is to define dedicated sections for both __devinit and
If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
other disabled, you end up with a reference between __init and a regular
non-init function.
My plan is to define dedicated sections for both __devinit and
On Tue, Jun 12, 2007 at 10:50:33AM +0900, Yasunori Goto wrote:
If CONFIG_MEMORY_HOTPLUG=n __meminit == __init, and if
CONFIG_HOTPLUG_CPU=n __cpuinit == __init. However, with one set and the
other disabled, you end up with a reference between __init and a regular
non-init function.
On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
> On Mon, 11 Jun 2007 13:35:43 +0900
> Paul Mundt <[EMAIL PROTECTED]> wrote:
>
> > When building with memory hotplug enabled and cpu hotplug disabled, we
> > end up with the following section mismatch:
> >
> > WARNING:
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt <[EMAIL PROTECTED]> wrote:
> When building with memory hotplug enabled and cpu hotplug disabled, we
> end up with the following section mismatch:
>
> WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
> .init.text: (between
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt [EMAIL PROTECTED] wrote:
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the following section mismatch:
WARNING: mm/built-in.o(.text+0x4e58): Section mismatch: reference to
.init.text: (between
On Mon, Jun 11, 2007 at 02:01:45PM +0900, KAMEZAWA Hiroyuki wrote:
On Mon, 11 Jun 2007 13:35:43 +0900
Paul Mundt [EMAIL PROTECTED] wrote:
When building with memory hotplug enabled and cpu hotplug disabled, we
end up with the following section mismatch:
WARNING:
14 matches
Mail list logo
