linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jgarzik@pobox.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	linux-net@vger.kernel.org
Subject: Re: Regarding SET_NETDEV_DEV
Date: Tue, 03 Jun 2003 20:09:44 -0700 (PDT)	[thread overview]
Message-ID: <20030603.200944.78736971.davem@redhat.com> (raw)
In-Reply-To: <20030603175921.GE2079@gtf.org>

   From: Jeff Garzik <jgarzik@pobox.com>
   Date: Tue, 3 Jun 2003 13:59:21 -0400

   For janitors and other developers placing this in net drivers...
   please don't :)  This can be done in upper layers, accomplishing the
   same goal without changing the low-level net driver code at all.
   
Don't say something can be done without showing exactly
how :-)

How does register_netdevice() know that the device is "whatever" and
where to get the generic device struct from?


  reply	other threads:[~2003-06-04  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 17:59 Regarding SET_NETDEV_DEV Jeff Garzik
2003-06-04  3:09 ` David S. Miller [this message]
2003-06-04  3:27   ` Jeff Garzik
2003-06-04  3:45   ` Stephen Hemminger
2003-06-04  3:46     ` David S. Miller

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=20030603.200944.78736971.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).