netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Al Viro <viro@ftp.linux.org.uk>, Jeff Garzik <jeff@garzik.org>,
	netdev@vger.kernel.org
Subject: Re: dgrs: sparse warnings
Date: Thu, 6 Sep 2007 15:30:38 +0200	[thread overview]
Message-ID: <20070906133038.GI16317@baikonur.stro.at> (raw)
In-Reply-To: <20070906135547.13bb3326@oldman>

On Thu, Sep 06, 2007 at 01:55:47PM +0100, Stephen Hemminger wrote:
> The dgrs driver is crap and assumes direct access to PCI iomem.
> 

dgrs wants to be removed, it has no users.
(no bug report in bugzilla nor in debian nor in google)
the firmware is not distrutable.

i'll resend my removal patch bzipped and attached.

-- 
maks

  reply	other threads:[~2007-09-06 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 12:55 dgrs: sparse warnings Stephen Hemminger
2007-09-06 13:30 ` maximilian attems [this message]
2007-09-06 13:50   ` [patch] dgrs removal maximilian attems
2007-09-06 14:16     ` maximilian attems
2007-09-06 14:24       ` maximilian attems

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=20070906133038.GI16317@baikonur.stro.at \
    --to=max@stro.at \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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).