From: Valdis.Kletnieks@vt.edu
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: David Miller <davem@davemloft.net>,
jeff@garzik.org, mchan@broadcom.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] bnx2: factor out gzip unpacker
Date: Fri, 21 Sep 2007 14:36:52 -0400 [thread overview]
Message-ID: <15775.1190399812@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 21 Sep 2007 19:05:23 BST." <200709211905.23946.vda.linux@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
On Fri, 21 Sep 2007 19:05:23 BST, Denys Vlasenko said:
> I plan to use gzip compression on following drivers' firmware,
> if patches will be accepted:
>
> text data bss dec hex filename
> 17653 109968 240 127861 1f375 drivers/net/acenic.o
> 6628 120448 4 127080 1f068 drivers/net/dgrs.o
> ^^^^^^
Should this be redone to use the existing firmware loading framework to
load the firmware instead?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-09-21 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 11:01 Denys Vlasenko
2007-09-21 11:03 ` [PATCH 2/2] bnx2: move gzip unpacker to zlib Denys Vlasenko
2007-09-21 16:14 ` [PATCH 1/2] bnx2: factor out gzip unpacker David Miller
2007-09-21 17:03 ` Denys Vlasenko
2007-09-21 17:49 ` David Miller
2007-09-21 18:05 ` Denys Vlasenko
2007-09-21 18:36 ` Valdis.Kletnieks [this message]
2007-09-21 19:18 ` Denys Vlasenko
2007-09-21 19:32 ` Valdis.Kletnieks
2007-09-21 19:33 ` Krzysztof Oledzki
2007-09-21 22:43 ` Denys Vlasenko
2007-09-21 22:57 ` Jeff Garzik
2007-09-21 21:03 ` Alan Cox
2007-09-21 22:33 ` Jeff Garzik
2007-09-21 22:48 ` Alan Cox
2007-09-22 0:02 ` maximilian attems
2007-09-21 20:13 ` Andi Kleen
2007-09-21 20:31 ` Roland Dreier
2007-09-21 22:37 ` Denys Vlasenko
2007-09-24 17:32 ` Lennart Sorensen
2007-09-25 4:20 ` Kyle Moffett
2007-09-22 2:47 ` Michael Chan
2007-10-01 0:57 ` David Miller
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=15775.1190399812@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vda.linux@googlemail.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
all inboxes | Powered by JetHome®