From: Stephen Hemminger <stephen.hemminger@vyatta.com>
To: eus@member.fsf.org
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: The ATN TP4/CLNP Networking Suite for GNU Linux systems
Date: Fri, 18 Jul 2008 14:41:42 -0700 [thread overview]
Message-ID: <20080718144142.4b19c7ff@speedy> (raw)
In-Reply-To: <488108C9.9050605@goop.org>
There is a nice documented process for submitting new drivers/protocols, (see Documentation/SubmittingPatches).
Developers really don't like to spend time looking at code in outside sites. You need to format the code
up as a set of patches to the current kernel and send them in email.
prev parent reply other threads:[~2008-07-18 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 15:30 The ATN TP4/CLNP Networking Suite for GNU Linux systems Eus
2008-07-18 21:19 ` Jeremy Fitzhardinge
2008-07-18 21:41 ` Stephen Hemminger [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=20080718144142.4b19c7ff@speedy \
--to=stephen.hemminger@vyatta.com \
--cc=eus@member.fsf.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.