From: Denys Vlasenko <vda.linux@googlemail.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Matthew Wilcox <matthew@wil.cx>,
Denys Vlasenko <vda.linux@googlemail.com>,
Arjan van de Ven <arjan@infradead.org>,
Adrian Bunk <bunk@kernel.org>, Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] debloat aic7xxx and aic79xx drivers
Date: Fri, 31 Aug 2007 16:13:59 +0100 [thread overview]
Message-ID: <200708311613.59666.vda.linux@googlemail.com> (raw)
On Friday 31 August 2007 14:42, Hannes Reinecke wrote:
> Jan Engelhardt wrote:
> > On Aug 30 2007 13:02, Matthew Wilcox wrote:
> >>> Well, you can send it to Linus/Andrew, that will usually upset people
> >>> and they start commenting on it. Or they don't, and everything is fine.
> >>> (The "default y" approach so to speak ;-)
> >>
> >> The problem is that we don't really have a maintainer for the aic7xyz
> >> drivers any more. Volunteers welcome. NOT IT!
> >
> > Take it before someone else does!
>
> Well, the semi-official maintainers are James B. and me.
>
> So I might as well do it officially.
Cool.
Thanks to Arjan's insistence, I also took a look at adding statics
and unexpectedly discovered yet another 50 kbytes of dead code
(I'm not kidding).
Attached are three patches which fix that:
text data bss dec hex filename
261433 50018 1172 312623 4c52f linux-2.6.23-rc1.org.t/drivers/scsi/aic7xxx/built-in.o
199654 50018 1172 250844 3d3dc linux-2.6.23-rc1.aic.t/drivers/scsi/aic7xxx/built-in.o
184014 21314 1172 206500 326a4 linux-2.6.23-rc1.aic1.t/drivers/scsi/aic7xxx/built-in.o
202378 2850 1172 206400 32640 linux-2.6.23-rc1.aic2.t/drivers/scsi/aic7xxx/built-in.o
1-debloat.patch deinlines a lot of functions
2-addstatic.patch adds statics, #ifdefs out huge amount of unused code, adds consts
3-addconst.patch adds more consts
make namespacecheck goes from 400+ functions to:
drivers/scsi/aic7xxx/aic79xx_core.o
ahd_inq
ahd_inw
ahd_outq
ahd_outw
drivers/scsi/aic7xxx/aic79xx_osm.o
ahd_insb
drivers/scsi/aic7xxx/aic7xxx_core.o
ahc_inq
ahc_outq
drivers/scsi/aic7xxx/aic7xxx_osm.o
ahc_insb
None of these patches actually touch any logic, code changes
are pretty minimal.
Compile tested and applies cleanly to 2.6.23-rc1, applies with some fuzz to 2.6.23-rc3.
Please propagate to mainline.
--
vda
next reply other threads:[~2007-08-31 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 15:13 Denys Vlasenko [this message]
2007-08-31 15:15 ` [PATCH 1/3] debloat aic7xxx and aic79xx drivers Denys Vlasenko
2007-08-31 15:16 ` [PATCH 2/3] " Denys Vlasenko
2007-08-31 15:17 ` [PATCH 3/3] " Denys Vlasenko
2007-09-24 10:24 ` Hannes Reinecke
2007-09-24 10:23 ` [PATCH 2/3] " Hannes Reinecke
2007-09-24 10:16 ` [PATCH 1/3] " Hannes Reinecke
2007-08-31 16:27 ` [PATCH 0/3] " Valdis.Kletnieks
2007-08-31 21:20 ` Denys Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2007-10-14 14:58 Denys Vlasenko
2007-10-14 17:47 ` Gabriel C
2007-10-15 11:25 ` Denys Vlasenko
2007-10-16 22:01 ` Gabriel C
2007-10-15 13:53 ` Gabriel C
2007-10-18 11:19 ` Denys Vlasenko
2007-10-18 21:31 ` J.A. Magallón
2008-03-23 3:40 Denys Vlasenko
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=200708311613.59666.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@kernel.org \
--cc=hare@suse.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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