netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Dykman <dykmanj@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] Host Fabric Interface (HFI) device driver available on sourceforge
Date: Sun, 31 Oct 2010 15:43:14 -0400	[thread overview]
Message-ID: <4CCDC6D2.4050207@linux.vnet.ibm.com> (raw)
In-Reply-To: <20101030.210806.232732630.davem@davemloft.net>

On 10/31/2010 12:08 AM, David Miller wrote:
> From: Jim Dykman<dykmanj@linux.vnet.ibm.com>
> Date: Sat, 30 Oct 2010 23:10:27 -0400
>
>> The HFI network interface is the internal cluster fabric of IBM's
>> PERCS supercomputer. The device driver patch for 2.6.36, hfi-utils,
>> and an introduction to the hardware are available on the sourceforge
>> page (http://sourceforge.net/projects/hfidevicedriver). The hardware
>> design is under US export control, so we cannot release hardware
>> specs.
>
> Nobody is going to look at your code, let alone help review it
> for inclusion, if you just say "go look at this stuff on this
> sourceforge web site."
>
> You have to post the kernel patches here, one by one.

Sorry, thought I was following the instructions for large patches in 
Documentation/SubmittingPatches. It is currently one patch of about 
22000 lines, around 630k.

Most of the patch is new files, I'm figuring one file per email.
There are 2 files just under 3000 lines, 4 in the 1000-1700 line range, 
and some smaller ones. Do I need to break any of those up further?

Jim Dykman


      reply	other threads:[~2010-10-31 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31  3:10 [ANNOUNCE] Host Fabric Interface (HFI) device driver available on sourceforge Jim Dykman
2010-10-31  4:08 ` David Miller
2010-10-31 19:43   ` Jim Dykman [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=4CCDC6D2.4050207@linux.vnet.ibm.com \
    --to=dykmanj@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).