Re: wrongly marked __init/__initdata for CPU hotplug

On Wed, Jan 25, 2006 at 12:02:53PM -0800, Ashok Raj wrote:
> Hi Andrew
> 
> attached patch is 2 more cases i found via running the reference_init.pl
> script. These were easy to spot just knowing the file names. There is 
> one another about init/main.c that i cant exactly zero in. (partly 
> because i dont know how to interpret the data thats spewed out of the tool).

I think that's the reference to __initcall_start / end 
That one is unavoidable, but not a bug.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: wrongly marked __init/__initdata for CPU hotplug
    • From: "Randy.Dunlap" <[email protected]>

• References:
  • wrongly marked __init/__initdata for CPU hotplug
    • From: Ashok Raj <[email protected]>

• Prev by Date: Re: [PATCH 5/6] fix warning on test_ti_thread_flag()
• Next by Date: Re: wrongly marked __init/__initdata for CPU hotplug
• Previous by thread: Re: wrongly marked __init/__initdata for CPU hotplug
• Next by thread: Re: wrongly marked __init/__initdata for CPU hotplug
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]