qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 00/28] Memory API for 1.6: fix I/O port endianne


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH 00/28] Memory API for 1.6: fix I/O port endianness mess
Date: Thu, 25 Jul 2013 12:25:45 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7

Il 25/07/2013 12:23, Benjamin Herrenschmidt ha scritto:
> On Thu, 2013-07-25 at 10:38 +0100, Peter Maydell wrote:
>> On 25 July 2013 10:00, Benjamin Herrenschmidt <address@hidden> wrote:
>>> That's fine, I know you can fix stuff :-) I'm just really annoyed that
>>> upstream qemu remained broken for so long (and still is) while the whole
>>> thing derailed into a mostly pointless discussion on endianness and
>>> nobody (including Alexey) hollered loud enough that the breakage was
>>> fairly extensive
>>
>> I think that for the minor architectures we just have to make
>> sure that we do yell loudly when things are broken, because
>> the nature of things is that people won't notice. Maybe we should
>> have a qemu-urgent list to parallel qemu-trivial for compile
>> fixes, reversions of bad breakage, etc, to try to keep them
>> out of the general noise ?
> 
> Or I teach Alexey to yell louder (along with some French :-)
> 
> Not sure if a mailing list is useful. A tag might be enough
> [REGRESSION] ? [URGENT] ? Those kind of subject tags tend to stand out
> pretty well on mailing lists.

I've definitely seen them already in the past on qemu-devel, so I concur
that a mailing list is not useful.

Paolo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]