From: David Gibson <dgibson@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Dmitry Fleytman <dmitry@daynix.com>,
qemu-ppc@nongnu.org, qemu-s390x@nongnu.org, f4bug@amsat.org
Subject: Re: [Qemu-devel] [PATCH v2 for-2.11] hw/net/vmxnet3: Fix code to work on big endian hosts, too
Date: Thu, 16 Nov 2017 10:18:04 +1100 [thread overview]
Message-ID: <20171116101804.5e24336f@umbus.fritz.box> (raw)
In-Reply-To: <8360a4ac-421d-1150-5e4c-cac5e2f7bdb3@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Wed, 15 Nov 2017 07:59:31 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 15.11.2017 00:33, David Gibson wrote:
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
> [...]
>
> David, I agree with all of your comments - I had similar thoughts when I
> was working with the code. However, as you already indicated, to address
> all of this, we would need to rewrite most parts of this device. That's
> out of my scope here - I wanted to keep the changes as minimal as
> possible, so that there is a chance that we can get the endianness
> problem still fixed for 2.11. So do you think that the patch is OK for
> this? ... otherwise, I think I'll rather send a patch that removes the
> vmxnet3 from the pxe-tester again - then it won't be tested anymore and
> we won't get anymore endianness test failures.
Yeah, good point. Getting a fix in place is more important than
making the existing stuff more elegant.
Reviewed-by: David Gibson <dgibson@redhat.com>
--
David Gibson <dgibson@redhat.com>
Principal Software Engineer, Virtualization, Red Hat
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-15 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 11:20 [Qemu-devel] [PATCH v2 for-2.11] hw/net/vmxnet3: Fix code to work on big endian hosts, too Thomas Huth
2017-11-14 11:41 ` Philippe Mathieu-Daudé
2017-11-14 11:59 ` no-reply
2017-11-14 23:33 ` David Gibson
2017-11-15 6:59 ` Thomas Huth
2017-11-15 23:18 ` David Gibson [this message]
2017-11-17 9:50 ` Jason Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171116101804.5e24336f@umbus.fritz.box \
--to=dgibson@redhat.com \
--cc=dmitry@daynix.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).