From: Roland Dreier <rdreier@cisco.com>
To: "Tom Tucker" <tom@opengridcomputing.com>
Cc: "Glenn Grundstrom" <ggrundstrom@NetEffect.com>,
netdev@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] [PATCH 1/5] NetEffect 10Gb RNIC Userspace Library: userspace config generation
Date: Fri, 27 Oct 2006 10:56:45 -0700 [thread overview]
Message-ID: <ada7iyl63s2.fsf@cisco.com> (raw)
In-Reply-To: <1161959235.2748.1.camel@trinity.ogc.int> (Tom Tucker's message of "Fri, 27 Oct 2006 09:27:15 -0500")
> I don't think the userspace stuff belongs on netdev. Someone please
> correct me if I'm wrong.
Yeah, it's not a bad thing to get wider review, but your userspace
library is pretty much your business. If you screw it up it doesn't
hurt anyone else, so I'm happy to let you write it however you want.
- R.
next prev parent reply other threads:[~2006-10-27 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 0:41 [PATCH 1/5] NetEffect 10Gb RNIC Userspace Library: userspace config generation Glenn Grundstrom
2006-10-27 14:27 ` Tom Tucker
2006-10-27 17:56 ` Roland Dreier [this message]
2006-10-27 18:01 ` [openib-general] " 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=ada7iyl63s2.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ggrundstrom@NetEffect.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=tom@opengridcomputing.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).