mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Langås" <tlan@stud.ntnu.no>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: tlan@stud.ntnu.no, linux-kernel@vger.kernel.org
Subject: Re: BCM5700, 1000 Mbps driver
Date: Mon, 11 Jun 2001 23:35:30 +0200	[thread overview]
Message-ID: <20010611233530.B10927@flodhest.stud.ntnu.no> (raw)
In-Reply-To: <20010611230603.A10927@flodhest.stud.ntnu.no> <E159Z1v-0000OH-00@the-village.bc.nu>
In-Reply-To: <E159Z1v-0000OH-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Jun 11, 2001 at 10:15:23PM +0100

Alan Cox:
> > * Are there anyone testing/maintaing this driver, trying to get it into the
> >   standard kernel source?
> Not right now that I know of. Nobody who read the source code did anything
> more constructive than run to throw up.

Are there any places (besides other drivers in the kernel) to look for
documents on how to write module-drivers/in-kernel drivers? 

> > * If not, would it be rude for me to make it work with the latest kernels,
> >   and then submitt it? (I won't take credit for anything I haven't done, but
> >   since I haven't written the driver itself, I don't know what you guys think)
> It does want a lot of clean up as well but go for it. I'm sure you will get
> plenty of comments on what needs cleaning up

Should I start by giving people a link to the source code? ;)  We need this
driver by the end of this summer, so I thought that making something that
could go in the std. kernel-tree was the best way of doing things. That way
we don't have to patch stuff each time either.

-- 
-Thomas

  reply	other threads:[~2001-06-11 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 21:06 Thomas Langås
2001-06-11 21:15 ` Alan Cox
2001-06-11 21:35   ` Thomas Langås [this message]
2001-06-11 22:09     ` Alan Cox
2001-06-11 23:35       ` Thomas Langås

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=20010611233530.B10927@flodhest.stud.ntnu.no \
    --to=tlan@stud.ntnu.no \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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

all inboxes | Powered by JetHome®