mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: "Németh Márton" <nm127@freemail.hu>
Cc: LKML <linux-kernel@vger.kernel.org>, Helge Deller <deller@gmx.de>,
	linux-input@vger.kernel.org
Subject: Re: __initdata and struct dmi_system_id?
Date: Sun, 14 Sep 2008 08:33:16 -0300	[thread overview]
Message-ID: <20080914113316.GA27289@khazad-dum.debian.net> (raw)
In-Reply-To: <48CCBD83.1030001@freemail.hu>

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.

-- 
  "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

  reply	other threads:[~2008-09-14 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  5:45 Németh Márton
2008-09-08 16:46 ` __initdata and struct dmi_system_id? [w/PATCH] Helge Deller
2008-09-14  7:30 ` __initdata and struct dmi_system_id? Németh Márton
2008-09-14 11:33   ` Henrique de Moraes Holschuh [this message]
2008-09-14 16:26     ` Németh Márton
2008-09-14 18:38       ` Henrique de Moraes Holschuh

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=20080914113316.GA27289@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=deller@gmx.de \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm127@freemail.hu \
    /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®