From: "Peter Hüwe" <PeterHuewe@gmx.de>
To: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: Thomas Winischhofer <thomas@winischhofer.net>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] video/sis: Use SiS_DRAMType from init.h and annotate it __devinitconst
Date: Thu, 3 May 2012 23:40:33 +0200 [thread overview]
Message-ID: <201205032340.34483.PeterHuewe@gmx.de> (raw)
In-Reply-To: <4FA1BF76.8080109@gmx.de>
Hi Florian,
> As far as I can see it should be possible to keep the array in
> sis_main.c and just delete it in the header files, shouldn't it? I'd
> prefer to do it this way.
Yes it is absolutely possible to leave it in sis_main.c and remove it from the
header files. I already thought about this when creating the patch, but
decided against it, as the 17*5 = 85 bytes are allocated on the stack, while
they nicely can be put in the .devinit.rodata section ;)
With the patch:
344072 sis_main.o
1200950 sisfb.o
1217491 sisfb.ko
vs without the patch and removing it only from the header:
344176 sis_main.o
1201056 sisfb.o
1217597 sisfb.ko -> ~100bytes more in the final module.
However I'm fine with this and will remove it from the header and squash this
together with the
"video/sis: Remove unused structs SiS_SDRDRAM_TYPE/SiS_DDRDRAM_TYPE"
I also sent to you.
Thanks,
Peterq
next prev parent reply other threads:[~2012-05-03 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 21:10 [PATCH 1/2] video/sis: Use SiS_DRAMType from init.h and annotate it __devinitconst Peter Huewe
2012-04-15 21:10 ` [PATCH 2/2] video/sis: Remove unused structs SiS_SDRDRAM_TYPE/SiS_DDRDRAM_TYPE Peter Huewe
2012-04-29 20:26 ` [PATCH v2] video/sis: Use SiS_DRAMType from init.h and annotate it __devinitconst Peter Huewe
2012-05-02 23:12 ` Florian Tobias Schandinat
2012-05-03 21:40 ` Peter Hüwe [this message]
2012-05-03 21:48 ` Florian Tobias Schandinat
2012-05-03 21:58 ` Peter Hüwe
2012-05-03 22:14 ` [PATCH] video/sis: Annotate SiS_DRAMType as __devinitconst Peter Huewe
2012-05-10 0:19 ` Florian Tobias Schandinat
2012-05-10 21:39 ` Peter Hüwe
2012-05-13 13:04 ` Florian Tobias Schandinat
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=201205032340.34483.PeterHuewe@gmx.de \
--to=peterhuewe@gmx.de \
--cc=FlorianSchandinat@gmx.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@winischhofer.net \
/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;
as well as URLs for NNTP newsgroup(s).