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:<bill.fisher@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: Wed, 4 Nov 2009 16:29:03 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: Bill Fisher <bill.fisher@lsi.com>, Brian Stark <brian.stark@lsi.com>,
 Rendell Fong <rendell.fong@lsi.com>
Subject: tuxstor kernel build
Message-ID: <20091104162903.4a480d11@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

Just so we're clear amongst ourselves, there was *nothing* special in my
checkin that makes the kernel build.  It included two changes from the
dev branch that weren't in the tuxrx branch yet, but those weren't
affecting the build, they were affecting the functioning.

All one had to do to get the kernel to build before my checkin was
comment out by hand a couple of function calls to eliminate a
couple of undefined symbols, which is pretty close to what I did.

If something is broken (I did boot test it) by doing that, then we will
have to wait for Bill's stuff because the special sauce is in there.
But this won't be a completely uncommon occurrance due to the stage of
development we're in.  Bill, Rendell and I seem to be completely
unphased by it for some reason.