X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7A33A.BCD8E2D9@onstor-exch02.onstor.net>; Wed, 30 May 2007 21:18:27 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7A33A.BCD8E2D9"
References: <BB375AF679D4A34E9CA8DFA650E2B04E02215803@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Shared header files: proposal for location
Date: Wed, 30 May 2007 21:18:27 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E032587D0@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Shared header files: proposal for location
Thread-Index: AcejI9FF72Qd8roBShKTvZ12zHqGUAAFjekV
From: "Richard Beck" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=RICHARD+2EBECK@onstor.com>
To: "Larry Scheer" <larry.scheer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>,
	"Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7A33A.BCD8E2D9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


That would work for me.=20
I had put them in include/net/neteee, but that hasn't even been checked =
in yet, so this is a good time to make this decision.
-rb

-----Original Message-----
From: Larry Scheer
Sent: Wed 5/30/2007 6:34 PM
To: Andy Sharp; Maxim Kozlovsky; Richard Beck; Tim Gardner
Cc: Larry Scheer
Subject: Shared header files: proposal for location
=20
I have been thinking about where to put the header files that are shared =
between the kernel build and the nfx-tree build. I think we all agree we =
don't want to put them in /usr/mipsel-linux-gnu/include.

I would like to see them placed in nfx-tree/Includes/linux. I see Max =
has already started putting header files there.=20

Given that lots of nfx-tree code includes neteee/eee.h it would be easy =
to add a neteee directory to nfx-tree/Includes. Also the Makefiles for =
the nfx-tree already accommodate this structure and are using this =
macro:

INCDIRS +=3D -I./$(OS) -I$(PATH_TO_ROOT)/Includes/$(OS)

CPPFLAGS    +=3D ${INCDIRS}

What do you think?

Larry


------_=_NextPart_001_01C7A33A.BCD8E2D9
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Shared header files: proposal for location</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT SIZE=3D2>That would work for me.<BR>
I had put them in include/net/neteee, but that hasn't even been checked =
in yet, so this is a good time to make this decision.<BR>
-rb<BR>
<BR>
-----Original Message-----<BR>
From: Larry Scheer<BR>
Sent: Wed 5/30/2007 6:34 PM<BR>
To: Andy Sharp; Maxim Kozlovsky; Richard Beck; Tim Gardner<BR>
Cc: Larry Scheer<BR>
Subject: Shared header files: proposal for location<BR>
<BR>
I have been thinking about where to put the header files that are shared =
between the kernel build and the nfx-tree build. I think we all agree we =
don't want to put them in /usr/mipsel-linux-gnu/include.<BR>
<BR>
I would like to see them placed in nfx-tree/Includes/linux. I see Max =
has already started putting header files there.<BR>
<BR>
Given that lots of nfx-tree code includes neteee/eee.h it would be easy =
to add a neteee directory to nfx-tree/Includes. Also the Makefiles for =
the nfx-tree already accommodate this structure and are using this =
macro:<BR>
<BR>
INCDIRS +=3D -I./$(OS) -I$(PATH_TO_ROOT)/Includes/$(OS)<BR>
<BR>
CPPFLAGS&nbsp;&nbsp;&nbsp; +=3D ${INCDIRS}<BR>
<BR>
What do you think?<BR>
<BR>
Larry<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7A33A.BCD8E2D9--
