public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Stefan Rompf <srompf@isg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interface operative status detection
Date: Fri, 08 Feb 2002 05:16:22 -0500	[thread overview]
Message-ID: <3C63A576.9D3AA89D@mandrakesoft.com> (raw)
In-Reply-To: <3C498CC9.6FAED2AF@isg.de>

Stefan Rompf wrote:
> Note that there is still sourcecode in drivers/net that plays with
> IFF_RUNNING directly. As I don't own these cards, let me just list the
> files so that the maintainers can have a look: bmac.c,
> wan/lmc/lmc_main.c, wan/comx-proto-fr.c, tlan.c, eepro100.c,
> au1000_eth.c, tokenring/ibmtr.c and bonding.c.

I recently fixed this in eepro100.c, in 2.4.18-pre9 and later.  Patches
accepted to clear up the others.


> diff -urN -X dontdiff linux-2.4.17/drivers/net/tulip/21142.c linux-2.4.17stefan/drivers/net/tulip/21142.c
> --- linux-2.4.17/drivers/net/tulip/21142.c      Fri Nov  9 22:45:35 2001
> +++ linux-2.4.17stefan/drivers/net/tulip/21142.c        Sat Jan 19 15:28:57 

thanks, patch applied and modified slightly, to 2.4 and 2.5.

-- 
Jeff Garzik      | "I went through my candy like hot oatmeal
Building 1024    |  through an internally-buttered weasel."
MandrakeSoft     |             - goats.com

  parent reply	other threads:[~2002-02-08 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19 15:12 Interface operative status detection Stefan Rompf
2002-01-19 15:29 ` Jeff Garzik
2002-01-19 18:34 ` Roberto Nibali
2002-02-08 10:16 ` Jeff Garzik [this message]
     [not found] <3C498CC9.6FAED2AF@isg.de.suse.lists.linux.kernel>
2002-01-19 17:40 ` Andi Kleen
2002-01-20  0:51   ` Stefan Rompf
2002-02-12 14:52   ` David L. Parsley
2002-02-12 15:58     ` Chris Friesen
2002-02-12 16:08       ` Stefan Rompf

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=3C63A576.9D3AA89D@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srompf@isg.de \
    /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