mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jiri Kosina <jkosina@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: Bloatwatch 2.6.28-rc1: i8042 DMI lookup tables
Date: Sat, 25 Oct 2008 09:20:25 +0100	[thread overview]
Message-ID: <1224922825.18031.16.camel@macbook.infradead.org> (raw)
In-Reply-To: <1224905479.3248.126.camel@calx>

On Fri, 2008-10-24 at 22:31 -0500, Matt Mackall wrote:
> Ideally, we'd find a way to (a) store variable-length string constants
> in init sections and (b) teach modpost about following pointers.

Doing (b) shouldn't be _so_ hard. Modpost already trawls through the
relocations, looking for naughty ones. Making it actually _do_ them when
it needs to shouldn't be impossible.

> Something like this would work inside code but sadly not inside
> declarations:
> 
> #define ISTR(s) ({static char c[] __attribute__ ((section("__initdata__"))) = s;c;})

Yeah, I played with that for a while, but gave up.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation


  reply	other threads:[~2008-10-25  8:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 20:25 Matt Mackall
2008-10-24 22:15 ` Jiri Kosina
2008-10-24 23:13   ` Matt Mackall
2008-10-25  0:46     ` Dmitry Torokhov
2008-10-25  3:31       ` Matt Mackall
2008-10-25  8:20         ` David Woodhouse [this message]
2008-10-26  0:28       ` Jiri Kosina
2008-10-25  8:14     ` David Woodhouse

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=1224922825.18031.16.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpm@selenic.com \
    /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

Powered by JetHome