From: Joe Perches <joe@perches.com>
To: Francois Romieu <romieu@fr.zoreil.com>,
Joel Soete <soete.joel@scarlet.be>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-kernel@vger.kernel.org, JBottomley@parallels.com,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Joel Soete <soete.joel@scarlet.be>
Subject: Re: [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100
Date: Thu, 17 May 2012 15:50:24 -0700 [thread overview]
Message-ID: <1337295024.8872.33.camel@joe2Laptop> (raw)
In-Reply-To: <20120517222843.GA30680@electric-eye.fr.zoreil.com>
On Fri, 2012-05-18 at 00:28 +0200, Francois Romieu wrote:
> Joe Perches <joe@perches.com> :
> > On Thu, 2012-05-17 at 17:20 -0400, Paul Gortmaker wrote:
> > > [Re: [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA
> >
> > If we're removing really old and unused stuff,
> > how about the VG/AnyLAN driver too?
>
> Joel Soete appeared to actively use a PCI one with recent kernels back
> in 2007.
I saw people using TR adapters with Linux as of 2008/9.
That doesn't mean it's common or make it desirable to
keep TR in the current kernel tree though.
Is VG/AnyLAN different?
next prev parent reply other threads:[~2012-05-17 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337272841-25931-1-git-send-email-paul.gortmaker@windriver.com>
2012-05-17 16:40 ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA Paul Gortmaker
2012-05-17 16:51 ` Paul Gortmaker
2012-05-17 21:20 ` Paul Gortmaker
2012-05-17 22:09 ` [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100 Joe Perches
2012-05-17 22:28 ` Francois Romieu
2012-05-17 22:50 ` Joe Perches [this message]
2012-05-18 19:28 ` Francois Romieu
2012-05-19 19:28 ` Joel Soete
2012-06-12 12:36 ` Pavel Machek
2012-05-17 22:23 ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA David Miller
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=1337295024.8872.33.camel@joe2Laptop \
--to=joe@perches.com \
--cc=JBottomley@parallels.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=romieu@fr.zoreil.com \
--cc=soete.joel@scarlet.be \
/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).