From: David Miller <davem@davemloft.net>
To: ktpedre@sandia.gov
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] seastar - SeaStar Ethernet driver
Date: Thu, 04 Feb 2010 17:04:48 -0800 (PST) [thread overview]
Message-ID: <20100204.170448.149507765.davem@davemloft.net> (raw)
In-Reply-To: <1265330214.23523.78.camel@hawkeye.sandia.gov>
From: "Kevin Pedretti" <ktpedre@sandia.gov>
Date: Thu, 4 Feb 2010 17:36:54 -0700
> Sure, I'm open to doing this and would appreciate any example drivers
> you could point me at.
I can't think of any sorry.
> We do need to keep the capability though of talking to Cray's
> existing proprietary "ethernet" over seastar driver, which the
> existing driver does. If we go this route of being a non-Ethernet
> device, do you think it would still be possible to support this?
I don't think it will break communication with Cray's stuff.
next prev parent reply other threads:[~2010-02-05 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 20:58 [PATCH] seastar - SeaStar Ethernet driver Kevin Pedretti
2010-02-02 21:42 ` David Miller
2010-02-03 1:24 ` Kevin Pedretti
2010-02-03 1:40 ` David Miller
2010-02-03 1:41 ` David Miller
2010-02-04 23:01 ` Kevin Pedretti
2010-02-04 23:13 ` David Miller
2010-02-05 0:36 ` Kevin Pedretti
2010-02-05 1:04 ` David Miller [this message]
2010-02-04 23:16 ` Alan Cox
2010-02-05 0:59 ` Kevin Pedretti
2010-02-03 16:12 ` Randy Dunlap
2010-02-02 21:59 ` Randy Dunlap
2010-02-02 22:12 ` Ben Hutchings
2010-02-02 23:38 ` Stephen Hemminger
2010-02-03 1:08 ` [PATCH] seastar - SeaStar Ethernet driver (review comments addressed) Kevin Pedretti
2010-02-03 1:39 ` Stephen Hemminger
2010-02-03 2:02 ` Joe Perches
2010-02-03 2:07 ` Stephen Hemminger
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=20100204.170448.149507765.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ktpedre@sandia.gov \
--cc=linux-kernel@vger.kernel.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 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).