public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thunder from the hill <thunder@ngforever.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Driver migration question
Date: Thu, 25 Jan 2001 09:59:12 -0700	[thread overview]
Message-ID: <3A705B60.B9BF6A3F@ngforever.de> (raw)
In-Reply-To: <14958.64899.320875.11952@somanetworks.com>

The way drivers have to be done is mixed of two aspects:
1. The way you do drivers and
2. the way the driver works.
You should also try not to rewrite existing functions for not to get a
mess of e.g. memory allocation functions that do the same but have
different names.
Georg Nikodym wrote:
> 
> So, rather than repeated ask questions of the form:
> 
>         How do I change X (a 2.2 thingy in my driver) to the blessed
>         form on 2.4.x?
> 
> I'm wondering if there's a driver in the kernel tree that somebody can
> point to and say, "This is how drivers should be done."  In
> particular, I'm interested in networking drivers but any non-trivial
> driver will do.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-25 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 16:06 Driver migration question Georg Nikodym
2001-01-25 16:59 ` Thunder from the hill [this message]

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=3A705B60.B9BF6A3F@ngforever.de \
    --to=thunder@ngforever.de \
    --cc=linux-kernel@vger.kernel.org \
    /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