From: maximilian attems <max@stro.at>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Miller <davem@davemloft.net>,
hpa@zytor.com, mchan@broadcom.com, vda.linux@googlemail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: bnx2 dirver's firmware images
Date: Wed, 19 Sep 2007 19:10:33 +0200 [thread overview]
Message-ID: <20070919171033.GH6618@stro.at> (raw)
In-Reply-To: <20070918203530.GC27836@uranus.ravnborg.org>
On Tue, 18 Sep 2007, Sam Ravnborg wrote:
> Anyway - if we again consider klibc I will do my best to make the
> build stuff as smooth as possible.
>
> Sam
<nitpicking mode on>
currently klibc has tendency to rebuild a bit too much if you
touch some part of it, seen in usr/utils
for the main klibc i agree that it makes sense
--
maks
next prev parent reply other threads:[~2007-09-19 17:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 17:23 bnx2 dirver's firmware images Denys Vlasenko
2007-09-18 18:45 ` Michael Chan
2007-09-18 17:55 ` Denys Vlasenko
2007-09-18 19:09 ` Michael Chan
2007-09-18 18:23 ` David Miller
2007-09-18 18:41 ` H. Peter Anvin
2007-09-18 19:20 ` David Miller
2007-09-18 19:27 ` H. Peter Anvin
2007-09-18 20:08 ` David Miller
2007-09-18 20:35 ` Sam Ravnborg
2007-09-18 20:40 ` H. Peter Anvin
2007-09-19 17:10 ` maximilian attems [this message]
2007-09-19 17:12 ` H. Peter Anvin
2007-09-19 17:18 ` maximilian attems
2007-09-19 17:37 ` Sam Ravnborg
2007-09-18 20:05 ` Michael Chan
2007-09-18 19:21 ` David Miller
2007-09-18 21:30 ` Willy Tarreau
2007-09-18 21:31 ` David Miller
2007-09-18 21:37 ` Willy Tarreau
2007-09-18 23:14 ` Michael Chan
2007-09-19 13:40 ` Bill Davidsen
2007-09-19 16:09 ` David Miller
2007-09-19 8:30 ` Denys Vlasenko
2007-09-19 21:00 ` Michael Chan
2007-09-19 20:29 ` Denys Vlasenko
2007-09-19 21:43 ` Michael Chan
2007-09-20 14:49 ` Denys Vlasenko
2007-09-21 2:12 ` Michael Chan
2007-09-19 16:33 ` maximilian attems
2007-09-19 16:38 ` David Miller
2007-09-19 16:51 ` maximilian attems
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=20070919171033.GH6618@stro.at \
--to=max@stro.at \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.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