@@ -37,7 +37,7 @@ Audit each individual driver, make sure it'll work with the generic
3737implementation (there's lots of outdated locking leftovers in various
3838implementations), and then remove it.
3939
40- Contact: Daniel Vetter, respective driver maintainers
40+ Contact: Simona Vetter, respective driver maintainers
4141
4242Level: Intermediate
4343
@@ -61,7 +61,7 @@ do by directly using the new atomic helper driver callbacks.
6161 .. [2 ] https://lwn.net/Articles/653071/
6262 .. [3 ] https://lwn.net/Articles/653466/
6363
64- Contact: Daniel Vetter, respective driver maintainers
64+ Contact: Simona Vetter, respective driver maintainers
6565
6666Level: Advanced
6767
@@ -75,7 +75,7 @@ helper should also be moved from drm_plane_helper.c to the atomic helpers, to
7575avoid confusion - the other helpers in that file are all deprecated legacy
7676helpers.
7777
78- Contact: Ville Syrjälä, Daniel Vetter, driver maintainers
78+ Contact: Ville Syrjälä, Simona Vetter, driver maintainers
7979
8080Level: Advanced
8181
@@ -97,7 +97,7 @@ with the current helpers:
9797- Then we could go through all the drivers and remove the more-or-less confused
9898 checks for plane_state->fb and plane_state->crtc.
9999
100- Contact: Daniel Vetter
100+ Contact: Simona Vetter
101101
102102Level: Advanced
103103
@@ -116,7 +116,7 @@ Somewhat related is the legacy_cursor_update hack, which should be replaced with
116116the new atomic_async_check/commit functionality in the helpers in drivers that
117117still look at that flag.
118118
119- Contact: Daniel Vetter, respective driver maintainers
119+ Contact: Simona Vetter, respective driver maintainers
120120
121121Level: Advanced
122122
@@ -169,7 +169,7 @@ interfaces to fix these issues:
169169 ``_helper_funcs `` since they are not part of the core ABI. There's a
170170 ``FIXME `` comment in the kerneldoc for each such case in ``drm_crtc.h ``.
171171
172- Contact: Daniel Vetter
172+ Contact: Simona Vetter
173173
174174Level: Intermediate
175175
@@ -194,7 +194,7 @@ performance-critical drivers it might also be better to go with a more
194194fine-grained per-buffer object and per-context lockings scheme. Currently only
195195the ``msm `` and `i915 ` drivers use ``struct_mutex ``.
196196
197- Contact: Daniel Vetter, respective driver maintainers
197+ Contact: Simona Vetter, respective driver maintainers
198198
199199Level: Advanced
200200
@@ -251,7 +251,7 @@ being rewritten without dependencies on the fbdev module. Some of the
251251helpers could further benefit from using struct iosys_map instead of
252252raw pointers.
253253
254- Contact: Thomas Zimmermann <
[email protected] >,
Daniel Vetter
254+ Contact: Thomas Zimmermann <
[email protected] >,
Simona Vetter
255255
256256Level: Advanced
257257
@@ -297,7 +297,7 @@ Various hold-ups:
297297 version of the varios drm_gem_fb_create functions. Maybe called
298298 drm_gem_fb_create/_with_dirty/_with_funcs as needed.
299299
300- Contact: Daniel Vetter
300+ Contact: Simona Vetter
301301
302302Level: Intermediate
303303
@@ -329,7 +329,7 @@ everything after it has done the write-protect/mkwrite trickery:
329329
330330Might be good to also have some igt testcases for this.
331331
332- Contact: Daniel Vetter, Noralf Tronnes
332+ Contact: Simona Vetter, Noralf Tronnes
333333
334334Level: Advanced
335335
@@ -359,7 +359,7 @@ between setting up the &drm_driver structure and calling drm_dev_register().
359359
360360- Once all drivers are converted, remove the load/unload callbacks.
361361
362- Contact: Daniel Vetter
362+ Contact: Simona Vetter
363363
364364Level: Intermediate
365365
@@ -422,7 +422,7 @@ The task is to use struct iosys_map where it makes sense.
422422* TTM might benefit from using struct iosys_map internally.
423423* Framebuffer copying and blitting helpers should operate on struct iosys_map.
424424
425- Contact: Thomas Zimmermann <
[email protected] >, Christian König,
Daniel Vetter
425+ Contact: Thomas Zimmermann <
[email protected] >, Christian König,
Simona Vetter
426426
427427Level: Intermediate
428428
@@ -558,7 +558,7 @@ This is a really varied tasks with lots of little bits and pieces:
558558 <https://lore.kernel.org/lkml/[email protected] /> `_
559559 for some example code that could be reused.
560560
561- Contact: Daniel Vetter
561+ Contact: Simona Vetter
562562
563563Level: Advanced
564564
@@ -587,7 +587,7 @@ There's a bunch of issues with it:
587587 this (together with the drm_minor->drm_device move) would allow us to remove
588588 debugfs_init.
589589
590- Contact: Daniel Vetter
590+ Contact: Simona Vetter
591591
592592Level: Intermediate
593593
@@ -608,7 +608,7 @@ Both these problems can be solved by switching over to drmm_kzalloc(), and the
608608various convenience wrappers provided, e.g. drmm_crtc_alloc_with_planes(),
609609drmm_universal_plane_alloc(), ... and so on.
610610
611- Contact: Daniel Vetter
611+ Contact: Simona Vetter
612612
613613Level: Intermediate
614614
@@ -628,7 +628,7 @@ cache is also tied to &drm_gem_object.import_attach. Meanwhile we paper over
628628this problem for USB devices by fishing out the USB host controller device, as
629629long as that supports DMA. Otherwise importing can still needlessly fail.
630630
631- Contact: Thomas Zimmermann <
[email protected] >,
Daniel Vetter
631+ Contact: Thomas Zimmermann <
[email protected] >,
Simona Vetter
632632
633633Level: Advanced
634634
@@ -709,7 +709,7 @@ Plan to fix this:
7097092. In all, only look at one of the three status bits set by the above helpers.
7107103. Remove the other two status bits.
711711
712- Contact: Daniel Vetter
712+ Contact: Simona Vetter
713713
714714Level: Intermediate
715715
0 commit comments