All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Michal Marek <mmarek@suse.cz>, Joe Perches <joe@perches.com>,
	One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Quentin Casasnovas <quentin.casasnovas@oracle.com>,
	Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: mod_devicetable: Make dmi_strmatch.substr const char *
Date: Thu, 21 May 2015 06:01:03 +0930	[thread overview]
Message-ID: <87twv7c7p4.fsf@rustcorp.com.au> (raw)
In-Reply-To: <555C36D1.4060003@suse.cz>

Michal Marek <mmarek@suse.cz> writes:
> Dne 20.5.2015 v 13:19 Rusty Russell napsal(a):
>> Joe Perches <joe@perches.com> writes:
>>> On Tue, 2015-05-19 at 16:56 +0100, One Thousand Gnomes wrote:
>>>> On Tue, 19 May 2015 07:46:58 +0100 David Woodhouse <dwmw2@infradead.org> wrote:
>>>>> On Mon, 2015-05-18 at 17:07 -0700, Joe Perches wrote:
>>>>>> changed dmi_strmatch.substr from char * to char[79];
>>>>>>
>>>>>> Changing it back to const char * would shrink an x86-64
>>>>>> defconfig more than 100KB.
>
> As David already pointed out, this breaks modpost. Also, what makes
> the dmi tables special? We use character arrays in other tables as
> well, to make them self-contained for modpost.

Yes, but the patch I referred to merely shrunk it, or changed
it to a pointer in the !CONFIG_MODULES case.

modpost has gotten far more sophisticated, thanks mainly to the
init section detection code.  So it now knows about relocations;
it would be possible to use the same infrastructure to decode
char *, and I think it might be worth it.

It'd be a nice trick if someone were to code it :)

>> But it seems the file2alias code was rewritten in 2013 by Andreas Schwab
>> <schwab@linux-m68k.org>, and SOB Michal Marek <mmarek@suse.cz>, without
>> going through me.  Annoying, since they had to hack it because people
>> screwed up mod_devicetable.h with arch-dependent layouts :(
>
> Oh, sorry about it.
>
>> I guess that means Michal is the maintainer now, so I've CC'd him.
>
> OK, fine, I can carry modpost patches in kbuid.git. I think I have
> merged a few more besides the file2alias rework.

Sure, let's do that from now on; I was a bit surprised but I'm always
happy for others to do my work for me :)

Thanks,
Rusty.

      parent reply	other threads:[~2015-05-20 20:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  0:07 mod_devicetable: Make dmi_strmatch.substr const char * Joe Perches
2015-05-19  6:46 ` David Woodhouse
2015-05-19 15:56   ` One Thousand Gnomes
2015-05-19 19:19     ` Joe Perches
2015-05-20  5:19       ` Rusty Russell
2015-05-20  7:25         ` Michal Marek
2015-05-20  7:58           ` Joe Perches
2015-05-20 20:31           ` Rusty Russell [this message]

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=87twv7c7p4.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dwmw2@infradead.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=quentin.casasnovas@oracle.com \
    --cc=schwab@linux-m68k.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.