Re: [Xen-devel] [qemu-s390x] [Qemu-devel] [PATCH v7 33/42] exec: Replace device_endian with MemOp
On 8/16/19 9:37 AM, tony.ngu...@bt.com wrote: > Simplify endianness comparisons with consistent use of the more > expressive MemOp. > > Suggested-by: Richard Henderson > Signed-off-by: Tony Nguyen > Reviewed-by: Richard Henderson > Acked-by: David Gibson This patch is *huge*, more than 800kB. It keeps being stuck in the the filter of the qemu-s390x list each time you send it. Please: 1) Try to break it up in more digestible pieces, e.g. change only one subsystem at a time (this is also better reviewable by people who are interested in one area) 2) Do not send HTML emails to the mailing list. Thanks, Thomas ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [qemu-s390x] [Qemu-devel] [PATCH v7 33/42] exec: Replace device_endian with MemOp
On 16/08/19 12:12, Thomas Huth wrote: > This patch is *huge*, more than 800kB. It keeps being stuck in the the > filter of the qemu-s390x list each time you send it. Please: > > 1) Try to break it up in more digestible pieces, e.g. change only one > subsystem at a time (this is also better reviewable by people who are > interested in one area) This is not really possible, since the patch is basically a search-and-replace. You could perhaps use some magic ("DEVICE_MEMOP_ENDIAN" or something like that) to allow a split, but it would introduce more complication than anything else. Agreed on the HTML though. :) Paolo ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [qemu-s390x] [Qemu-devel] [PATCH v7 33/42] exec: Replace device_endian with MemOp
On 19/08/19 20:28, Paolo Bonzini wrote: > On 16/08/19 12:12, Thomas Huth wrote: >> This patch is *huge*, more than 800kB. It keeps being stuck in the the >> filter of the qemu-s390x list each time you send it. Please: >> >> 1) Try to break it up in more digestible pieces, e.g. change only one >> subsystem at a time (this is also better reviewable by people who are >> interested in one area) > > This is not really possible, since the patch is basically a > search-and-replace. You could perhaps use some magic > ("DEVICE_MEMOP_ENDIAN" or something like that) to allow a split, but it > would introduce more complication than anything else. I'm stupid, at this point of the series it _would_ be possible to split the patch by subsystem. Still not sure it would be actually an advantage. Paolo > Agreed on the HTML though. :) > > Paolo > ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel