From: Jon Mason <jdmason@us.ibm.com>
To: jgarzik@pobox.com
Cc: netdev@oss.sgi.com
Subject: No Maintainer entry for dl2k driver
Date: Fri, 17 Dec 2004 16:13:43 -0600 [thread overview]
Message-ID: <200412171613.43330.jdmason@us.ibm.com> (raw)
It has come to my attention that there is no entry in the kernel MAINTAINERS
file for the D-Link Gigabit Ethernet Driver (and possibly no maintainer).
So, I have created a patch for that file with an entry for the driver status
as Orphaned.
--- MAINTAINERS.orig 2004-12-17 16:01:37.955336376 -0600
+++ MAINTAINERS 2004-12-17 16:07:21.027181528 -0600
@@ -704,6 +704,10 @@ M: mvw@planets.elm.net
L: linux-kernel@vger.kernel.org
S: Maintained
+DL2K NETWORK DRIVER
+L: linux-net@vger.kernel.org
+S: Orphan
+
DAVICOM FAST ETHERNET (DMFE) NETWORK DRIVER
P: Tobias Ringstrom
M: tori@unhappy.mine.nu
--
Jon Mason
jdmason@us.ibm.com
next reply other threads:[~2004-12-17 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 22:13 Jon Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-18 0:20 No Maintainer entry for dl2k driver Xose Vazquez Perez
2004-12-20 20:54 ` Jon Mason
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=200412171613.43330.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).