From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@lists.linuxppc.org>, Stefan Jeglinski <jeglin@4pi.com>
Subject: Re: ethtool failure with tulip 21143
Date: Thu, 27 Dec 2001 16:22:11 +0100 [thread overview]
Message-ID: <20011227152211.3321@smtp.noos.fr> (raw)
In-Reply-To: <p04330100b8504e9e9393@[66.57.250.32]>
>I remember even further contacting Donald Becker about somehow
>inserting this cache alignment fix into the tulip driver. No
>response. So, any thoughts on how to proceed? I have no idea how to
>get the fix into tulip to test...
>
I'll try to hack you something in tulip to test.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-27 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 17:53 ethtool failure with tulip 21143 Stefan Jeglinski
2001-12-16 18:13 ` Jeff Garzik
2001-12-16 18:37 ` Stefan Jeglinski
2001-12-16 21:59 ` Benjamin Herrenschmidt
2001-12-16 23:31 ` Stefan Jeglinski
2001-12-16 23:38 ` Benjamin Herrenschmidt
2001-12-27 4:13 ` Stefan Jeglinski
2001-12-27 13:41 ` Kevin B. Hendricks
2001-12-27 15:22 ` Benjamin Herrenschmidt [this message]
2001-12-16 18:25 ` Benjamin Herrenschmidt
2001-12-16 21:24 ` Tony 'Nicoya' Mantler
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=20011227152211.3321@smtp.noos.fr \
--to=benh@kernel.crashing.org \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).