mausezahn-libs = -lcli \ -lnet \ -lpcap \ -lrt \ -lpthread \ -lm mausezahn-objs = str.o \ die.o \ xmalloc.o \ staging/layer1.o \ staging/layer2.o \ staging/layer3.o \ staging/layer4.o \ staging/hextools.o \ staging/tools.o \ staging/lookupdev.o \ staging/time.o \ staging/modifications.o \ staging/send_eth.o \ staging/send.o \ staging/cdp.o \ staging/rtp.o \ staging/dns.o \ staging/rcv_rtp.o \ staging/syslog.o \ staging/cli.o \ staging/cli_cmds.o \ staging/cli_launch.o \ staging/cli_legacy.o \ staging/cli_packet.o \ staging/cli_interface.o \ staging/cli_set.o \ staging/cli_dns.o \ staging/cli_arp.o \ staging/cli_bpdu.o \ staging/cli_eth.o \ staging/cli_ip.o \ staging/cli_udp.o \ staging/cli_tcp.o \ staging/cli_rtp.o \ staging/cli_tools.o \ staging/cli_igmp.o \ staging/cli_lldp.o \ staging/cli_sequence.o \ staging/mops.o \ staging/mops_update.o \ staging/mops_tools.o \ staging/mops_checksums.o \ staging/mops_threads.o \ staging/mops_dot1Q.o \ staging/mops_mpls.o \ staging/mops_ip.o \ staging/mops_tcp.o \ staging/mops_ext.o \ staging/mops_ext_arp.o \ staging/mops_ext_bpdu.o \ staging/mops_ext_rtp.o \ staging/mopsrx_arp.o \ staging/mops_ext_igmp.o \ staging/mops_ext_lldp.o \ staging/mops_sequence.o \ staging/automops.o \ staging/parse_xml.o \ staging/tx_switch.o \ staging/llist.o \ staging/directmops.o \ staging/mausezahn.o mausezahn-eflags = -O2 -I. -I.. \ -DVERSION_STRING=\"$(VERSION_STRING)\" \ -DVERSION_LONG=\"$(VERSION_LONG)\" mausezahn-confs = efslogtreecommitdiff
path: root/include/uapi/scsi/Kbuild
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-12 17:15:56 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-30 10:17:32 +0100
commite6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 (patch)
tree77cadb6d8aad1b52c34e4afa8c9deef603bbe2ed /include/uapi/scsi/Kbuild
parent4e5b54f127426c82dc2816340c26d951a5bb3429 (diff)
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 'include/uapi/scsi/Kbuild')