On Thu, Jun 8, 2017 at 10:16 PM, Markus Armbruster wrote:
> Alistair Francis writes:
>
>> On Thu, Jun 8, 2017 at 10:56 AM, Markus Armbruster wrote:
>>> Alistair Francis writes:
>>>
On Wed, Jun
Alistair Francis writes:
> On Thu, Jun 8, 2017 at 10:56 AM, Markus Armbruster wrote:
>> Alistair Francis writes:
>>
>>> On Wed, Jun 7, 2017 at 11:03 PM, Markus Armbruster
>>> wrote:
Alistair
On Thu, Jun 8, 2017 at 10:56 AM, Markus Armbruster wrote:
> Alistair Francis writes:
>
>> On Wed, Jun 7, 2017 at 11:03 PM, Markus Armbruster wrote:
>>> Alistair Francis writes:
>>>
On Wed, Jun
Alistair Francis writes:
> On Wed, Jun 7, 2017 at 11:03 PM, Markus Armbruster wrote:
>> Alistair Francis writes:
>>
>>> On Wed, Jun 7, 2017 at 12:19 AM, Markus Armbruster
>>> wrote:
Paolo
On Wed, Jun 7, 2017 at 11:03 PM, Markus Armbruster wrote:
> Alistair Francis writes:
>
>> On Wed, Jun 7, 2017 at 12:19 AM, Markus Armbruster wrote:
>>> Paolo Bonzini writes:
>>>
On 06/06/2017 18:30,
Alistair Francis writes:
> On Wed, Jun 7, 2017 at 12:19 AM, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> On 06/06/2017 18:30, Alistair Francis wrote:
>
> This is somehow confusing. I don't think it is
On Wed, Jun 7, 2017 at 12:19 AM, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> On 06/06/2017 18:30, Alistair Francis wrote:
This is somehow confusing. I don't think it is worth having another
qemu_log_stderr() function rather than
Paolo Bonzini writes:
> On 06/06/2017 18:30, Alistair Francis wrote:
>>>
>>> This is somehow confusing. I don't think it is worth having another
>>> qemu_log_stderr() function rather than using error_report() but this very
>>> call might deserve a comment explaining this
On Tue, Jun 6, 2017 at 3:14 PM, Paolo Bonzini wrote:
>
>
> On 06/06/2017 18:30, Alistair Francis wrote:
>>>
>>> This is somehow confusing. I don't think it is worth having another
>>> qemu_log_stderr() function rather than using error_report() but this very
>>> call might
On 06/06/2017 18:30, Alistair Francis wrote:
>>
>> This is somehow confusing. I don't think it is worth having another
>> qemu_log_stderr() function rather than using error_report() but this very
>> call might deserve a comment explaining this unusual use. What do you think?
>
> The problem
On Tue, Jun 6, 2017 at 6:37 AM, Philippe Mathieu-Daudé wrote:
> On 06/06/2017 08:58 AM, Marc-André Lureau wrote:
>>
>> Hi
>>
>> On Mon, Jun 5, 2017 at 10:37 PM Alistair Francis <
>> alistair.fran...@xilinx.com> wrote:
>>
>>> When QEMU is waiting for a TCP socket connection it
On 06/06/2017 08:58 AM, Marc-André Lureau wrote:
Hi
On Mon, Jun 5, 2017 at 10:37 PM Alistair Francis <
alistair.fran...@xilinx.com> wrote:
When QEMU is waiting for a TCP socket connection it reports that message as
an error. This isn't an error though, so let's change the report to just
use
Hi
On Mon, Jun 5, 2017 at 10:37 PM Alistair Francis <
alistair.fran...@xilinx.com> wrote:
> When QEMU is waiting for a TCP socket connection it reports that message as
> an error. This isn't an error though, so let's change the report to just
> use qemu_log().
>
>
I don't think this is a good
On 06/05/2017 03:34 PM, Alistair Francis wrote:
When QEMU is waiting for a TCP socket connection it reports that message as
an error. This isn't an error though, so let's change the report to just
use qemu_log().
Signed-off-by: Alistair Francis
Reviewed-by:
When QEMU is waiting for a TCP socket connection it reports that message as
an error. This isn't an error though, so let's change the report to just
use qemu_log().
Signed-off-by: Alistair Francis
---
chardev/char-socket.c | 3 ++-
1 file changed, 2 insertions(+),
15 matches
Mail list logo