More important activities lacking, "Michael Smith" <smithmg@agere.com> wrote:
> That particular header is included. As I mentioned, I am using memset
> in other areas of the code, as well as the same file. If I take this
> one call out of the source, it compiles, links and I am able to perform
> and insmod correctly. Below are the headers that are included in the
> file, and the area of the code that is causing the problem. Let me say
> that the code, even with this particular call in, compiles and links.
> The problem happens when I go to perform the insmod on it.
>
> #include <memory.h>
> #include <string.h>
> #include "myownheaders.h"
>
>
> void myfunction( void *a, int len )
> {
> ....
> Mymemmove() //used because NdisMoveMemory can not be used
> memset( &a->WORD[NUMWORDS-len], 0, len*4);
> ...
> }
Inside a driver (or module) file, any include reference that doesn't begin with
either <linux/foo.h> or <asm/foo.h> should always raise a red flag. There are
user-land header files ("/usr/include") and kernel header files
("/usr/src/linux/include") and never the twain shall meet.
Mixing includes is always a bad idea.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + -- -- -- -- -- -- -- -- -- --
Tommy Reynolds | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone: +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA | FAX: +1.256.837.3839
Senior Software Developer | Mobile: +1.919.641.2923
--=.B/wcCO..sRzKww
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
iEYEARECAAYFAjwOcq8ACgkQWEn3bOOMcup7sQCdG4Zr4DAMAy5lJ4QvEsy+uHw+
bBMAn1PG7gYvYbIYlLJvRLVsFyNzNvS2
=z9l7
-----END PGP SIGNATURE-----
--=.B/wcCO..sRzKww--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/