Re: __initdata and struct dmi_system_id?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 14 Sep 2008, Németh Márton wrote:
> Henrique de Moraes Holschuh wrote:
> > On Sun, 14 Sep 2008, Németh Márton wrote:
> >> The other interesting question on this topic is that what about the
> >> error message strings which are used as parameter of the printk() calls.
> >> Those strings are combined together for a function which is marked with
> >> __init and the functions which are normal functions. The strings which
> >> are only used by the functions marked with __init could be freed, but
> >> the strings of the normal functions shouldn't be.
> > 
> > Yeah, if we could get them all in a init.rodata section, we could just throw
> > them away along with the init section afterwards...
> > 
> > I do think I have seen a patch about init.rodata in LKML not too long ago,
> > though.
> 
> Do you mean this one?

Yeah.  I don't know if it does (or is related to) what you want, though.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux