All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@linux-mips.org, netdev@oss.sgi.com
Subject: Re: "eth%d" - net dev name in 2.6?
Date: Wed, 10 Mar 2004 15:59:06 +0100	[thread overview]
Message-ID: <20040310145906.GA9104@linux-mips.org> (raw)
In-Reply-To: <20040310025346.GA5661@deprecation.cyrius.com>

On Wed, Mar 10, 2004 at 02:53:46AM +0000, Martin Michlmayr wrote:

> I have no idea, but I've seen a similar bug report at
> http://bugs.debian.org/234817

This affects drivers/net/ne.c, so I'm adding netdev to the cc list.

Same problem, dereferencing net_device->name before register_netdev().
That's caused by a bit toooo quick and sloopy conversion from
init_etherdev to alloc_etherdev & register_netdev.

  Ralf

  reply	other threads:[~2004-03-10 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10  2:33 "eth%d" - net dev name in 2.6? Jun Sun
2004-03-10  2:53 ` Martin Michlmayr
2004-03-10 14:59   ` Ralf Baechle [this message]
2004-03-10  4:14 ` Kumba
2004-03-10 14:59   ` Ralf Baechle
2004-03-10 22:17     ` Kumba
2004-03-10 14:51 ` Ralf Baechle

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=20040310145906.GA9104@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=netdev@oss.sgi.com \
    --cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.