From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Konstantin Volckov <goldhead@altlinux.ru>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Edward Peng." <edward_peng@dlink.com.tw>
Subject: Re: PATCH for dl2k driver
Date: Tue, 10 Jul 2001 15:17:38 -0400 [thread overview]
Message-ID: <3B4B54D2.9A81EDDD@mandrakesoft.com> (raw)
In-Reply-To: <20010710222417.26dedb99.goldhead@altlinux.ru>
Konstantin Volckov wrote:
> There is a mistake in dl2k.c network driver added in 2.4.6-ac2.
I doubt you have hardware for it, so no big deal ;-)
> Without this patch gcc-2.95.3 produces a broken symbol __ucmpdi2, while
> gcc-2.96 works ok.
Alan please do not apply, there is a better update coming your way,
including other bug fixes as well.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
prev parent reply other threads:[~2001-07-10 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-10 18:24 PATCH for dl2k driver Konstantin Volckov
2001-07-10 19:17 ` Jeff Garzik [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=3B4B54D2.9A81EDDD@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=edward_peng@dlink.com.tw \
--cc=goldhead@altlinux.ru \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox