| To: | Andrew Morton <andrewm@xxxxxxxxxx> |
|---|---|
| Subject: | Re: True on TRANSMIT ERROR TIMEOUT |
| From: | Andrey Savochkin <saw@xxxxxxxxxxxxx> |
| Date: | Thu, 15 Jun 2000 18:17:30 +0800 |
| Cc: | netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <39487F5B.D26F4AFF@uow.edu.au>; from "Andrew Morton" on Thu, Jun 15, 2000 at 07:01:47AM |
| References: | <39461BB3.299DD807@uow.edu.au> <Pine.LNX.4.10.10006141420380.370-100000@kenzo.iwr.uni-heidelberg.de> <39483426.B07E4BA@uow.edu.au>, <39483426.B07E4BA@uow.edu.au>; <20000615122401.B3638@saw.sw.com.sg> <39487F5B.D26F4AFF@uow.edu.au> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Thu, Jun 15, 2000 at 07:01:47AM +0000, Andrew Morton wrote:
> And some time ago Donald has pointed at a history of people putting in
> bandaids and claiming to have "fixed the problem" when they really have
> not.
Do not take it too seriously... :-)
> We would be very bad to do that.
>
> But there is real value in just keeping the damn things working.
>
> Perhaps 'stable' kernels should have the bandaids, and development
> kernels shouldn't.
If timeout routine is written, it should
1) work
2) be included in the driver independently of the kernel status.
Developers need user's reports, but it doesn't mean that the driver shouldn't
do its best to work even in case of problems. You'll get reports anyway.
I just mentioned the "bandaid" status of timeout routine to explain that this
topic is rather controversial.
Best regards
Andrey
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Tulip and IP aliasing, Jeff Garzik |
|---|---|
| Next by Date: | Re: Tulip and IP aliasing, Andi Kleen |
| Previous by Thread: | Re: True on TRANSMIT ERROR TIMEOUT, Andrew Morton |
| Next by Thread: | Re: [vortex, eepro100] True on TRANSMIT ERROR TIMEOUT, Tres Hofmeister |
| Indexes: | [Date] [Thread] [Top] [All Lists] |