public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "O.Sezer" <sezeroz@ttnet.net.tr>
To: "John W. Linville" <linville@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [netdrvr] netdev-2.4 queue updated
Date: Mon, 15 Nov 2004 22:44:01 +0200	[thread overview]
Message-ID: <41991511.1080006@ttnet.net.tr> (raw)
In-Reply-To: <20041115173245.GI14381@redhat.com>

John W. Linville wrote:
> On Mon, Nov 15, 2004 at 12:06:22PM -0500, Jeff Garzik wrote:
> 
>>O.Sezer wrote:
>>
>>>>John W. Linville:
>>>> o 3c59x: resync with 2.6
>>>>
>>>
>>>Any specific reason that the following two are not included ?
>>>
>>>3c59x: reload EEPROM values at rmmod for needy cards:
>>>http://marc.theaimsgroup.com/?l=linux-kernel&m=109726032213947&w=2
>>>
>>>3c59x: remove EEPROM_RESET for 3c905 :
>>>http://marc.theaimsgroup.com/?l=linux-kernel&m=109802672909516&w=2
>>
>>Ask John Linville...  IIRC they caused problems?
> 

I have two machines with 3c905's (Boomerang series) running with
Linville's 3 patches without any problems for more than 10 days I
think. But that's only me.

> Actually, the second one was there to correct the first one.
> (Only PART of the first patch was undone by the second one.)

I'm aware of that, thanks.

> They are additive, so they should be applied in the order above.
> If you'd prefer, I could gen-up a single patch?
> 
> Thanks,
> 
> John

Ozkan Sezer


  reply	other threads:[~2004-11-15 20:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 15:07 [netdrvr] netdev-2.4 queue updated O.Sezer
2004-11-15 17:06 ` Jeff Garzik
2004-11-15 17:32   ` John W. Linville
2004-11-15 20:44     ` O.Sezer [this message]
2004-11-15 22:49     ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15  6:46 Jeff Garzik

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=41991511.1080006@ttnet.net.tr \
    --to=sezeroz@ttnet.net.tr \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@redhat.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