mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-28 13:22:57 +00:00
drm/TODO: Clarify DRM_DEV_* conversion
Not everyone agrees this is the best thing, so make it really clear that maintainers need to be asked first, then the conversion. We've had a few newbies that did this the other way round, got their patches rejected, which isn't the best newbie experience. Cc: Sean Paul <seanpaul@chromium.org> Acked-by: Sean Paul <seanpaul@chromium.org> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20171030131536.11654-1-daniel.vetter@ffwll.ch
This commit is contained in:
parent
1de86387bc
commit
9f44678161
1 changed files with 4 additions and 0 deletions
|
@ -179,6 +179,10 @@ don't do this, drivers used dev_info/warn/err to make this differentiation. We
|
||||||
now have DRM_DEV_* variants of the drm print macros, so we can start to convert
|
now have DRM_DEV_* variants of the drm print macros, so we can start to convert
|
||||||
those drivers back to using drm-formwatted specific log messages.
|
those drivers back to using drm-formwatted specific log messages.
|
||||||
|
|
||||||
|
Before you start this conversion please contact the relevant maintainers to make
|
||||||
|
sure your work will be merged - not everyone agrees that the DRM dmesg macros
|
||||||
|
are better.
|
||||||
|
|
||||||
Contact: Sean Paul, Maintainer of the driver you plan to convert
|
Contact: Sean Paul, Maintainer of the driver you plan to convert
|
||||||
|
|
||||||
Core refactorings
|
Core refactorings
|
||||||
|
|
Loading…
Reference in a new issue