From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 27 ++-
1 file changed, 18 i
From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 27 ++-
1 file changed, 18 i
From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 27 ++-
1 file changed, 18 i
From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
Reviewed-by: Paolo Bonzini
---
qemu-char.c | 27 ++-
1 file changed, 18 i
Il 22/09/2014 01:04, miny...@acm.org ha scritto:
> From: Corey Minyard
>
> It seems that it might be a good idea to know what is at the remote
> end of a socket for tracking down issues. So add that to the
> socket filename.
>
> Signed-off-by: Corey Minyard
> ---
> qemu-char.c | 27 ++
From: Corey Minyard
It seems that it might be a good idea to know what is at the remote
end of a socket for tracking down issues. So add that to the
socket filename.
Signed-off-by: Corey Minyard
---
qemu-char.c | 27 ++-
1 file changed, 18 insertions(+), 9 deletions(-)