diff options
| author | Marcel J.E. Mol <marcel@mesa.nl> | 2017-01-30 19:26:40 +0100 |
|---|---|---|
| committer | Johan Hovold <johan@kernel.org> | 2017-01-31 17:27:04 +0100 |
| commit | d07830db1bdb254e4b50d366010b219286b8c937 (patch) | |
| tree | 354d7fca237fa3d7e7e63c2196eaa4e1086838ea /net/wireless/wext-compat.h | |
| parent | 5d03a2fd2292e71936c4235885c35ccc3c94695b (diff) | |
USB: serial: pl2303: add ATEN device ID
Seems that ATEN serial-to-usb devices using pl2303 exist with
different device ids. This patch adds a missing device ID so it
is recognised by the driver.
Signed-off-by: Marcel J.E. Mol <marcel@mesa.nl>
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Johan Hovold <johan@kernel.org>
Diffstat (limited to 'net/wireless/wext-compat.h')
drm: Don't race connector registration
I was under the misconception that the sysfs dev stuff can be fully
set up, and then registered all in one step with device_add. That's
true for properties and property groups, but not for parents and child
devices. Those must be fully registered before you can register a
child.
Add a bit of tracking to make sure that asynchronous mst connector
hotplugging gets this right. For consistency we rely upon the implicit
barriers of the connector->mutex, which is taken anyway, to ensure
that at least either the connector or device registration call will
work out.
Mildly tested since I can't reliably reproduce this on my mst box
here.
Reported-by: Dave Hansen <dave.hansen@intel.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/1484237756-2720-1-git-send-email-daniel.vetter@ffwll.ch
Diffstat (limited to 'tools/testing/ktest/ktest.pl')