All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Helge Deller <deller@gmx.de>, Jan Beulich <jbeulich@novell.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: __initdata and struct dmi_system_id?
Date: Sun, 14 Sep 2008 18:26:52 +0200	[thread overview]
Message-ID: <48CD3B4C.8010106@freemail.hu> (raw)
In-Reply-To: <20080914113316.GA27289@khazad-dum.debian.net>

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?

Date: Fri, 05 Sep 2008 13:03:17 +0100
From: Jan Beulich <jbeulich@novell.com>
Subject: [PATCH] .init.rodata and modpost adjustments
http://lkml.org/lkml/2008/9/5/126

Regards,

	Márton Németh
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: "Németh Márton" <nm127@freemail.hu>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Helge Deller <deller@gmx.de>, Jan Beulich <jbeulich@novell.com>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: __initdata and struct dmi_system_id?
Date: Sun, 14 Sep 2008 18:26:52 +0200	[thread overview]
Message-ID: <48CD3B4C.8010106@freemail.hu> (raw)
In-Reply-To: <20080914113316.GA27289@khazad-dum.debian.net>

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?

Date: Fri, 05 Sep 2008 13:03:17 +0100
From: Jan Beulich <jbeulich@novell.com>
Subject: [PATCH] .init.rodata and modpost adjustments
http://lkml.org/lkml/2008/9/5/126

Regards,

	Márton Németh

  reply	other threads:[~2008-09-14 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  5:45 __initdata and struct dmi_system_id? Németh Márton
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  7:30   ` Németh Márton
2008-09-14 11:33   ` Henrique de Moraes Holschuh
2008-09-14 11:33     ` Henrique de Moraes Holschuh
2008-09-14 16:26     ` Németh Márton [this message]
2008-09-14 16:26       ` Németh Márton
2008-09-14 18:38       ` Henrique de Moraes Holschuh
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=48CD3B4C.8010106@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=deller@gmx.de \
    --cc=hmh@hmh.eng.br \
    --cc=jbeulich@novell.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.