[RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe

2014-05-19 Thread David Herrmann
Hi CC: Dave & Daniel On Wed, May 14, 2014 at 3:58 PM, Jani Nikula wrote: > Hi all - > > This series stores connector/encoder names in the relevant structs to > make the name getters thread safe. > > What say you, is the wasted memory too high a price to pay for the > thread safety and implementa

[RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe

2014-05-14 Thread Jani Nikula
On Wed, 14 May 2014, Chris Wilson wrote: > On Wed, May 14, 2014 at 04:58:18PM +0300, Jani Nikula wrote: >> Hi all - >> >> This series stores connector/encoder names in the relevant structs to >> make the name getters thread safe. >> >> What say you, is the wasted memory too high a price to pay f

[RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe

2014-05-14 Thread Jani Nikula
Hi all - This series stores connector/encoder names in the relevant structs to make the name getters thread safe. What say you, is the wasted memory too high a price to pay for the thread safety and implementation simplicity of this approach? I think making drm_get_connector_name and drm_get_enco

[RFC PATCH 0/2] drm: make drm_get_{connector, encoder}_name thread safe

2014-05-14 Thread Chris Wilson
On Wed, May 14, 2014 at 04:58:18PM +0300, Jani Nikula wrote: > Hi all - > > This series stores connector/encoder names in the relevant structs to > make the name getters thread safe. > > What say you, is the wasted memory too high a price to pay for the > thread safety and implementation simplici