summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEric Anholt <eric@anholt.net>2011-09-21 09:27:51 -0700
committerEric Anholt <eric@anholt.net>2011-09-22 11:03:17 -0700
commitd58a3182b1e680105731897fe2d84928daf89fce (patch)
tree1aa902a47371d88c5b70e3bee8143694373f2727
parentbc0335fc0e0bd6a777ef16ad5245d35ccf7adcf6 (diff)
intel: Remove stale comment about non-intel gl_buffer_objects.
This hasn't been true since dd26899ca39111e0866afed9df94bfb1618dd363 in 2009. Reviewed-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
-rw-r--r--src/mesa/drivers/dri/intel/intel_buffer_objects.h9
1 files changed, 1 insertions, 8 deletions
diff --git a/src/mesa/drivers/dri/intel/intel_buffer_objects.h b/src/mesa/drivers/dri/intel/intel_buffer_objects.h
index b174e93443c..e74d0612475 100644
--- a/src/mesa/drivers/dri/intel/intel_buffer_objects.h
+++ b/src/mesa/drivers/dri/intel/intel_buffer_objects.h
@@ -84,14 +84,7 @@ void intel_upload_finish(struct intel_context *intel);
*/
void intelInitBufferObjectFuncs(struct dd_function_table *functions);
-
-
-/* Are the obj->Name tests necessary? Unfortunately yes, mesa
- * allocates a couple of gl_buffer_object structs statically, and
- * the Name == 0 test is the only way to identify them and avoid
- * casting them erroneously to our structs.
- */
-static INLINE struct intel_buffer_object *
+static inline struct intel_buffer_object *
intel_buffer_object(struct gl_buffer_object *obj)
{
return (struct intel_buffer_object *) obj;