summary refs log tree commit diff
path: root/devices
diff options
context:
space:
mode:
authorAlyssa Ross <hi@alyssa.is>2020-02-20 00:22:01 +0000
committerAlyssa Ross <hi@alyssa.is>2020-03-10 18:03:12 +0000
commitfbc11f247fa0d58f050daf02a8e9aaa4cab02caf (patch)
tree1db421852a0e425c4c301a7ca30d81c975bb6552 /devices
parent951c0833e002f37203a466054d397d3831b3e4e5 (diff)
downloadcrosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar.gz
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar.bz2
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar.lz
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar.xz
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.tar.zst
crosvm-fbc11f247fa0d58f050daf02a8e9aaa4cab02caf.zip
msg_socket: don't force array elements to be clone
There didn't seem to be any reason for this restriction.

From #crosvm:

<qyliss> Why does the implementation of MsgOnSocket for arrays require that elements be Clone?
<qyliss> It seems to work just fine if I remove the clone() call and Clone requirement
<zachr> I suspect that there is no good reason.
Diffstat (limited to 'devices')
0 files changed, 0 insertions, 0 deletions