From: Jeff Garzik <jgarzik@pobox.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: netdev@vger.kernel.org, paulus@samba.org,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove the broken OAKNET driver
Date: Thu, 18 Jan 2007 22:05:57 -0500 [thread overview]
Message-ID: <45B03595.2030604@pobox.com> (raw)
In-Reply-To: <20070104185330.GG20714@stusta.de>
Adrian Bunk wrote:
> The OAKNET driver:
> - has been marked as BROKEN for more than two years and
> - is still marked as BROKEN.
>
> Drivers that had been marked as BROKEN for such a long time seem to be
> unlikely to be revived in the forseeable future.
>
> But if anyone wants to ever revive this driver, the code is still
> present in the older kernel releases.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
applied
prev parent reply other threads:[~2007-01-19 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 18:53 [RFC: 2.6 patch] remove the broken OAKNET driver Adrian Bunk
2007-01-19 3:05 ` Jeff Garzik [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=45B03595.2030604@pobox.com \
--to=jgarzik@pobox.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.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).