netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maximilian attems <maks@sternwelten.at>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Nathanael Nerode <neroden@fastmail.fm>,
	Andres Salomon <dilinger@debian.org>
Subject: Re: RFC: removing the dgrs net driver
Date: Sat, 2 Dec 2006 18:31:36 +0100	[thread overview]
Message-ID: <20061202173136.GM30153@baikonur.stro.at> (raw)
In-Reply-To: <20061202171932.GP11084@stusta.de>

On Sat, Dec 02, 2006 at 06:19:32PM +0100, Adrian Bunk wrote:
> Based on the information in the email forwarded below I'd remove the 
> dgrs net driver (this wasn't the first driver shipped with the kernel 
> without any hardware ever produced...).
> 
> Is this OK or is there any doubt whether this information is true?
> 
> cu
> Adrian

ok thanks for doing this,
as the reporter was to lazy to cook up a proper patch for that.

there is zero bug report for dgrs on the debian bts nor did i find
one in bugzilla.kernel.org. redhat guys might want to verify on their
side.

 
> ----- Forwarded message from Nathanael Nerode <neroden@fastmail.fm> -----
> 
> Date:	Sun, 24 Sep 2006 13:00:12 -0400
> From: Nathanael Nerode <neroden@fastmail.fm>
> To: netdev@vger.kernel.org
> Subject: Please remove useless dgrs driver
> 
> An official email from digi.com to Andres Salomon <dilinger@debian.org>
> explained:
> 
>  Dear Andres:
> 
>  After further research, we found that this product was killed in place
>  and never reached the market.  We would like to request that this not be
>  included.
> 
> Copy at http://wiki.debian.org/KernelFirmwareLicensing (this was discovered
> during research into firmware licensing).
> 
> The drgs driver is useless (no hardware to drive) and should be removed.
> The files which should be deleted from the tree are:
>         drivers/net/dgrs.c
>         drivers/net/dgrs.h
>         drivers/net/dgrs_es4h.h
>         drivers/net/dgrs_plx9060.h
>         drivers/net/dgrs_i82596.h
>         drivers/net/dgrs_ether.h
>         drivers/net/dgrs_asstruct.h
>         drivers/net/dgrs_bcomm.h
>         drivers/net/dgrs_firmware.c
> 
> It will probably also be necessary to delete some stuff from drivers/net/Kconfig
> and drivers/net/Makefile, but I assume that this will be trivial for any
> net maintainer.
> 
> Thanks in advance for doing this.
> 
> -- 
> Nathanael Nerode  <neroden@fastmail.fm>
> 
> "(Instead, we front-load the flamewars and grudges in
> the interest of efficiency.)" --Steve Lanagasek,
> http://lists.debian.org/debian-devel/2005/09/msg01056.html
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> ----- End forwarded message -----
--
maks

      parent reply	other threads:[~2006-12-02 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-02 17:19 RFC: removing the dgrs net driver Adrian Bunk
2006-12-02 17:31 ` Alan
2006-12-02 17:31 ` maximilian attems [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=20061202173136.GM30153@baikonur.stro.at \
    --to=maks@sternwelten.at \
    --cc=bunk@stusta.de \
    --cc=dilinger@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neroden@fastmail.fm \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).