AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<bfisher@lsi.com>,<brian.stark@lsi.com>,<rendell.fong@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 1 Sep 2009 16:23:46 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: Bill Fisher <bfisher@lsi.com>
Cc: Brian Stark <brian.stark@lsi.com>, Rendell Fong <rendell.fong@lsi.com>
Subject: moving neteee2 back to kernel and other stuff
Message-ID: <20090901162346.76c1138e@ripper.onstor.net>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Bill,

As I told you several times, this is fine with me.  Just put together a
perforce changelist and send it to me and I'll look it over and if it's
cool, I'll give it the green light.  But if you want to do that, it has
to be independent, and by that I mean, not dependent on any symbols in
eee-anything or rcon-anything and so forth.  I think you get what I'm
driving at.  It will be OK for code in nfx-tree to be dependent on
neteee2 symbols, but not the other way around.

Rendell and I are working on finishing the current interation of this
stuff, and then we should be in a position to make some of these
changes you want.  He might ask you to take care of some issues that
come out of reviewing all this stuff, which is what I've been doing
yesterday and today.  I will probably have some code that needs fixing
up as well.

As for merging the tuxrx branch back into the dev tree, I really don't
see what you're trying to solve by pushing that now.  It can't be done
now, because we can't spend 87 man-years making the TXRX code
dual-buildable.  We have to get much closer to tuxstor being a real
product, at which point we can figure out how to do this.  It will
require a broader audience than just engineering, however, because
a phase out of the EEE based product goes part and parcel with that
move, and needs to be carefully thought through.  Doing an integrate
from dev into tuxrx branch right now won't be onerous, and it's
something Larry can take care of.  That should calm anyone's
fears about the two branches being too out of sync.  There's a couple
of changes to the sm-ui branch and they likely will land in areas that
you've axed anyway, so no worries there.

Cheers,

a
