On Monday, December 7th, 2020 at 11:00 AM, James Park <james.park@xxxxxxxxxxxxxxxx> wrote: > Not to make too big a deal of it, but the idea was that if you went > out of your way to define DRM_FOURCC_STANDALONE in your code base, > that you would also go through the pain of removing drm.h includes > elsewhere. It's too annoying of an implication to > document/communicate, so I'm happier with the other > DRM_FOURCC_STANDALONE solution that pulls the basic types into a > common header. In my compositors I'd like to globally define DRM_FOURCC_STANDALONE (to make sure I don't miss any #define) but I still may include drm.h in the same files as well. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
