Re: [Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
On Tue, May 27, 2003 at 09:43:32PM -0500, Leif Delgass wrote: > Don't worry about it, shit happens. ;) I fixed a couple of things that I > came across, and I'm doing a quick onceover through CVS web to > double-check. Great work with the documentation, btw. > > One minor issue I had: Can we keep the emacs mode magic for the drm files: > -*- linux-c -*- Sure. I've never used emacs so I didn't know the exact meaning of those. > This sets up the indentation and style in emacs if you have the mode > defined (as described in the kernel docs). It needs to be on the first > line of the file. Would it mess up doxygen to add a comment above the > header?, e.g.: > > /* -*- linux-c -*- */ > /** > * \file ... No, that should be fine. In this case I think I'll also add a vim modeline. Does the emacs mode line needs to be on in the first line, or can it be in the last one? It doesn't look so much intrusive that way. José Fonseca --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
Am Mittwoch, 28. Mai 2003 04:24 schrieb José Fonseca: > Sorry about that. I merged everything manually using a visual diff util > to prevent that this happened, and compiled everything after and > corrected the errors, but still failed. Thanks! Dieter --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
Don't worry about it, shit happens. ;) I fixed a couple of things that I came across, and I'm doing a quick onceover through CVS web to double-check. Great work with the documentation, btw. One minor issue I had: Can we keep the emacs mode magic for the drm files: -*- linux-c -*- This sets up the indentation and style in emacs if you have the mode defined (as described in the kernel docs). It needs to be on the first line of the file. Would it mess up doxygen to add a comment above the header?, e.g.: /* -*- linux-c -*- */ /** * \file ... --Leif On Wed, 28 May 2003, [iso-8859-15] José Fonseca wrote: > Sorry about that. I merged everything manually using a visual diff util > to prevent that this happened, and compiled everything after and > corrected the errors, but still failed. > > José Fonseca > > On Tue, May 27, 2003 at 08:46:04PM -0500, Leif Delgass wrote: > > Looks like the change to drm_os_linux.h that removed the argument from the > > DRM_*MEMORYBARRIER() macros was reverted with the documentation merge. I > > just checked in a fix. > > > > --Leif > > > > On Wed, 28 May 2003, Dieter [iso-8859-15] Nützel wrote: > > > > > Linux 2.4.21-rc2-jam1 > > > > > > r128_state.c:81: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:96: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:122: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:138: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:157: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:172: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:199: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:223: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:398: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:419: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:440: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:462: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:510: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:524: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:552: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:565: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:610: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:625: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:673: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:685: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:768: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:828: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:882: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:955: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:979: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:1073: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:1097: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:1144: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:1206: macro `DRM_WRITEMEMORYBARRIER' used without args > > > r128_state.c:1234: macro `DRM_WRITEMEMORYBARRIER' used without args > > > make[12]: *** [r128_state.o] Error 1 > > > > > > radeon_cp.c:728: macro `DRM_MEMORYBARRIER' used without args > > > radeon_cp.c:735: macro `DRM_MEMORYBARRIER' used without args > > > radeon_cp.c:753: macro `DRM_MEMORYBARRIER' used without args > > > radeon_cp.c:760: macro `DRM_MEMORYBARRIER' used without args > > > make[12]: *** [radeon_cp.o] Error 1 > > > > > > etc. > > > > > > Thanks, > > > Dieter > > > > > > > > > > > > --- > > > This SF.net email is sponsored by: ObjectStore. > > > If flattening out C++ or Java code to make your application fit in a > > > relational database is painful, don't do it! Check out ObjectStore. > > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > > ___ > > > Dri-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > > > > > -- > > Leif Delgass > > http://www.retinalburn.net > > > > > > > > --- > > This SF.net email is sponsored by: ObjectStore. > > If flattening out C++ or Java code to make your application fit in a > > relational database is painful, don't do it! Check out ObjectStore. > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > ___ > > Dri-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/dri-devel > -- Leif Delgass http://www.retinalburn.net -
Re: [Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
Sorry about that. I merged everything manually using a visual diff util to prevent that this happened, and compiled everything after and corrected the errors, but still failed. José Fonseca On Tue, May 27, 2003 at 08:46:04PM -0500, Leif Delgass wrote: > Looks like the change to drm_os_linux.h that removed the argument from the > DRM_*MEMORYBARRIER() macros was reverted with the documentation merge. I > just checked in a fix. > > --Leif > > On Wed, 28 May 2003, Dieter [iso-8859-15] Nützel wrote: > > > Linux 2.4.21-rc2-jam1 > > > > r128_state.c:81: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:96: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:122: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:138: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:157: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:172: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:199: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:223: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:398: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:419: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:440: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:462: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:510: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:524: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:552: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:565: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:610: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:625: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:673: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:685: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:768: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:828: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:882: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:955: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:979: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:1073: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:1097: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:1144: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:1206: macro `DRM_WRITEMEMORYBARRIER' used without args > > r128_state.c:1234: macro `DRM_WRITEMEMORYBARRIER' used without args > > make[12]: *** [r128_state.o] Error 1 > > > > radeon_cp.c:728: macro `DRM_MEMORYBARRIER' used without args > > radeon_cp.c:735: macro `DRM_MEMORYBARRIER' used without args > > radeon_cp.c:753: macro `DRM_MEMORYBARRIER' used without args > > radeon_cp.c:760: macro `DRM_MEMORYBARRIER' used without args > > make[12]: *** [radeon_cp.o] Error 1 > > > > etc. > > > > Thanks, > > Dieter > > > > > > > > --- > > This SF.net email is sponsored by: ObjectStore. > > If flattening out C++ or Java code to make your application fit in a > > relational database is painful, don't do it! Check out ObjectStore. > > Now part of Progress Software. http://www.objectstore.net/sourceforge > > ___ > > Dri-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/dri-devel > > > > -- > Leif Delgass > http://www.retinalburn.net > > > > --- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
Looks like the change to drm_os_linux.h that removed the argument from the DRM_*MEMORYBARRIER() macros was reverted with the documentation merge. I just checked in a fix. --Leif On Wed, 28 May 2003, Dieter [iso-8859-15] Nützel wrote: > Linux 2.4.21-rc2-jam1 > > r128_state.c:81: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:96: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:122: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:138: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:157: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:172: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:199: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:223: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:398: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:419: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:440: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:462: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:510: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:524: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:552: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:565: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:610: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:625: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:673: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:685: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:768: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:828: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:882: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:955: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:979: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:1073: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:1097: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:1144: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:1206: macro `DRM_WRITEMEMORYBARRIER' used without args > r128_state.c:1234: macro `DRM_WRITEMEMORYBARRIER' used without args > make[12]: *** [r128_state.o] Error 1 > > radeon_cp.c:728: macro `DRM_MEMORYBARRIER' used without args > radeon_cp.c:735: macro `DRM_MEMORYBARRIER' used without args > radeon_cp.c:753: macro `DRM_MEMORYBARRIER' used without args > radeon_cp.c:760: macro `DRM_MEMORYBARRIER' used without args > make[12]: *** [radeon_cp.o] Error 1 > > etc. > > Thanks, > Dieter > > > > --- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > ___ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel > -- Leif Delgass http://www.retinalburn.net --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [trunk] CVS compilation errors (DRM_WRITEMEMORYBARRIER)
Linux 2.4.21-rc2-jam1 r128_state.c:81: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:96: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:122: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:138: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:157: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:172: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:199: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:223: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:398: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:419: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:440: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:462: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:510: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:524: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:552: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:565: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:610: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:625: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:673: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:685: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:768: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:828: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:882: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:955: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:979: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:1073: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:1097: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:1144: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:1206: macro `DRM_WRITEMEMORYBARRIER' used without args r128_state.c:1234: macro `DRM_WRITEMEMORYBARRIER' used without args make[12]: *** [r128_state.o] Error 1 radeon_cp.c:728: macro `DRM_MEMORYBARRIER' used without args radeon_cp.c:735: macro `DRM_MEMORYBARRIER' used without args radeon_cp.c:753: macro `DRM_MEMORYBARRIER' used without args radeon_cp.c:760: macro `DRM_MEMORYBARRIER' used without args make[12]: *** [radeon_cp.o] Error 1 etc. Thanks, Dieter --- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
