From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>,
david@gibson.dropbear.id.au
Subject: Re: [PULL] virtio/vhost: cross endian support
Date: Fri, 3 Jul 2015 15:26:00 -0700 [thread overview]
Message-ID: <CA+55aFx6Rr8xWTKynja6Miuxhscc0QrfCGWgo4ZzbePCdeKjzA@mail.gmail.com> (raw)
In-Reply-To: <20150703095637-mutt-send-email-mst@redhat.com>
On Fri, Jul 3, 2015 at 12:59 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> Linus, could you please clarify whether making the
> feature depend on the cross-endian guest support
> would address your comment, and whether you think
> this can be merged as is, and the dependency added
> after -rc1?
I'll take it. I still think dynamic byte order is a fundamental (and
much too common) mistake, but whatever.
Linus
prev parent reply other threads:[~2015-07-03 22:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 9:31 [PULL] virtio/vhost: cross endian support Michael S. Tsirkin
2015-07-01 19:02 ` Linus Torvalds
2015-07-01 19:03 ` Linus Torvalds
2015-07-02 6:12 ` Michael S. Tsirkin
2015-07-02 6:01 ` Michael S. Tsirkin
2015-07-02 9:12 ` Greg Kurz
2015-07-02 9:32 ` Michael S. Tsirkin
2015-07-07 16:36 ` Thomas Huth
2015-07-07 16:51 ` Michael S. Tsirkin
2015-07-09 7:49 ` [PATCH] KVM: Add Kconfig option to signal cross-endian guests Thomas Huth
2015-07-09 9:48 ` Laurent Vivier
2015-07-09 12:57 ` Paolo Bonzini
2015-07-09 13:07 ` Michael S. Tsirkin
2015-07-09 18:59 ` Thomas Huth
2015-07-09 10:02 ` Christoffer Dall
2015-07-09 12:21 ` Cornelia Huck
2015-07-13 9:24 ` Greg Kurz
2015-07-03 7:59 ` [PULL] virtio/vhost: cross endian support Michael S. Tsirkin
2015-07-03 22:26 ` Linus Torvalds [this message]
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=CA+55aFx6Rr8xWTKynja6Miuxhscc0QrfCGWgo4ZzbePCdeKjzA@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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).