From: Joe Perches <joe@perches.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, JBottomley@parallels.com,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100
Date: Thu, 17 May 2012 15:09:07 -0700 [thread overview]
Message-ID: <1337292547.8872.20.camel@joe2Laptop> (raw)
In-Reply-To: <20120517212039.GC27789@windriver.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?
---
drivers/net/ethernet/Kconfig | 1 -
drivers/net/ethernet/Makefile | 1 -
drivers/net/ethernet/hp/Kconfig | 32 -
drivers/net/ethernet/hp/Makefile | 5 -
drivers/net/ethernet/hp/hp100.c | 3066 --------------------------------------
drivers/net/ethernet/hp/hp100.h | 615 --------
6 files changed, 0 insertions(+), 3720 deletions(-)
delete mode 100644 drivers/net/ethernet/hp/Kconfig
delete mode 100644 drivers/net/ethernet/hp/Makefile
delete mode 100644 drivers/net/ethernet/hp/hp100.c
delete mode 100644 drivers/net/ethernet/hp/hp100.h
diff --git a/drivers/net/ethernet/Kconfig b/drivers/net/ethernet/Kconfig
index a11af5c..0896c8f 100644
--- a/drivers/net/ethernet/Kconfig
+++ b/drivers/net/ethernet/Kconfig
@@ -52,7 +52,6 @@ source "drivers/net/ethernet/neterion/Kconfig"
source "drivers/net/ethernet/faraday/Kconfig"
source "drivers/net/ethernet/freescale/Kconfig"
source "drivers/net/ethernet/fujitsu/Kconfig"
-source "drivers/net/ethernet/hp/Kconfig"
source "drivers/net/ethernet/ibm/Kconfig"
source "drivers/net/ethernet/intel/Kconfig"
source "drivers/net/ethernet/i825xx/Kconfig"
diff --git a/drivers/net/ethernet/Makefile b/drivers/net/ethernet/Makefile
index 878ad32..756ebd3 100644
--- a/drivers/net/ethernet/Makefile
+++ b/drivers/net/ethernet/Makefile
@@ -27,7 +27,6 @@ obj-$(CONFIG_NET_VENDOR_EXAR) += neterion/
obj-$(CONFIG_NET_VENDOR_FARADAY) += faraday/
obj-$(CONFIG_NET_VENDOR_FREESCALE) += freescale/
obj-$(CONFIG_NET_VENDOR_FUJITSU) += fujitsu/
-obj-$(CONFIG_NET_VENDOR_HP) += hp/
obj-$(CONFIG_NET_VENDOR_IBM) += ibm/
obj-$(CONFIG_NET_VENDOR_INTEL) += intel/
obj-$(CONFIG_NET_VENDOR_I825XX) += i825xx/
next prev parent reply other threads:[~2012-05-17 22:09 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 ` Joe Perches [this message]
2012-05-17 22:28 ` [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100 Francois Romieu
2012-05-17 22:50 ` Joe Perches
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=1337292547.8872.20.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 \
/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).