Mesa (master): panfrost: Update spilling comment framebuffer->shared

[GitLab Mirror]

Module: Mesa
Branch: master
Commit: febabb0502605a7fa742cafc85c3c4c414d8001e
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=febabb0502605a7fa742cafc85c3c4c414d8001e

Author: Alyssa Rosenzweig <alyssa.rosenzweig at collabora.com>
Date:   Tue Feb 25 15:34:16 2020 -0500

panfrost: Update spilling comment framebuffer->shared

All of this should apply equally with compute shaders, as far as I know.

Signed-off-by: Alyssa Rosenzweig <alyssa.rosenzweig at collabora.com>
Reviewed-by: Tomeu Vizoso <tomeu.vizoso at collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3950>

---

 src/panfrost/encoder/pan_scratch.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/panfrost/encoder/pan_scratch.c b/src/panfrost/encoder/pan_scratch.c
index 780dd539be6..c75c1f330ef 100644
--- a/src/panfrost/encoder/pan_scratch.c
+++ b/src/panfrost/encoder/pan_scratch.c
@@ -48,7 +48,7 @@
  *
  * Within a particular thread, there is stack allocated. If it is present, its
  * size is a power-of-two, and it is at least 256 bytes. Stack is allocated
- * with the framebuffer descriptor used for all shaders within a frame (note
+ * with the shared memory descriptor used for all shaders within a frame (note
  * that they don't execute concurrently so it's fine). So, consider the maximum
  * stack size used by any shader within a job, and then compute (where npot
  * denotes the next power of two):