From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Christoph Raisch <RAISCH@de.ibm.com>
Cc: netdev@vger.kernel.org, MEDER@de.ibm.com, THEMANN@de.ibm.com
Subject: Re: new driver for IBM ethernet chip
Date: Fri, 2 Jun 2006 09:00:34 -0700 [thread overview]
Message-ID: <20060602090034.8f9bf036.rdunlap@xenotime.net> (raw)
In-Reply-To: <OFA75C1070.77D8B8F0-ONC125717F.003D730C-C1257181.003C592B@de.ibm.com>
On Fri, 2 Jun 2006 13:02:37 +0200 Christoph Raisch wrote:
> We're currently developing a new Ethernet device driver for a 10G IBM chip
> for System p. (ppc64)
>
> A later version of the driver should end up in mainline kernel.
> How should we proceed to get first comments by the community?
> Either post this code as a patch to netdev or
yes
> put a full tarball on for example sourceforge?
nope.
Please read and observe: Documentation/SubmittingPatches
and Section 3 of it, References, for other sources of
expectations/requirements.
The -mm tree also contains Documentation/SubmitChecklist
that you may find useful.
---
~Randy
prev parent reply other threads:[~2006-06-02 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 11:02 new driver for IBM ethernet chip Christoph Raisch
2006-06-02 16:00 ` Randy.Dunlap [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=20060602090034.8f9bf036.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=MEDER@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=THEMANN@de.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox