On Mar 20, 2021, at 17:16, Bhaskar Chowdhury unixbhaskar@gmail.com wrote:
s/particuar/particular/
Signed-off-by: Bhaskar Chowdhury unixbhaskar@gmail.com
drivers/gpu/drm/vmwgfx/vmwgfx_so.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_so.c b/drivers/gpu/drm/vmwgfx/vmwgfx_so.c index 7369dd86d3a9..6cd38e407145 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_so.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_so.c @@ -33,7 +33,7 @@
- The currently only reason we need to keep track of views is that if we
- destroy a hardware surface, all views pointing to it must also be destroyed,
- otherwise the device will error.
- So in particuar if a surface is evicted, we must destroy all views pointing
- So in particular if a surface is evicted, we must destroy all views pointing
- to it, and all context bindings of that view. Similarly we must restore
- the view bindings, views and surfaces pointed to by the views when a
- context is referenced in the command stream.
-- 2.26.2
Looks good. I’ll push it through the drm-misc tree on my next series. Unless of course you want to push it through a different tree in which case: Reviewed-by: Zack Rusin zackr@vmware.com
z