From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2 0/3] vhost: cross-endian code cleanup
Date: Tue, 16 Feb 2016 17:34:13 +0200 [thread overview]
Message-ID: <20160216153413.GA32554@redhat.com> (raw)
In-Reply-To: <20160216145418.7448.71329.stgit@bahia.lab.toulouse-stg.fr.ibm.com>
On Tue, Feb 16, 2016 at 03:54:18PM +0100, Greg Kurz wrote:
> This series is a new tentative to have cleaner cross-endian code.
>
> Patches 1/3 is new: it fixes a side-effect in case vhost_init_used() fails.
>
> Patch 2/3 comes from v1: it renames cross-endian helpers
>
> Patch 3/3 is new: it simply renames vhost_init_used() as suggested by Michael.
Is this on top of my tree?
> ---
>
> Greg Kurz (3):
> vhost: fix error path in vhost_init_used()
> vhost: rename cross-endian helpers
> vhost: rename vhost_init_used()
>
>
> drivers/vhost/net.c | 2 +-
> drivers/vhost/scsi.c | 2 +-
> drivers/vhost/test.c | 2 +-
> drivers/vhost/vhost.c | 49 +++++++++++++++++++++++++++++++++++++------------
> drivers/vhost/vhost.h | 2 +-
> 5 files changed, 41 insertions(+), 16 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2 0/3] vhost: cross-endian code cleanup
Date: Tue, 16 Feb 2016 17:34:13 +0200 [thread overview]
Message-ID: <20160216153413.GA32554@redhat.com> (raw)
In-Reply-To: <20160216145418.7448.71329.stgit@bahia.lab.toulouse-stg.fr.ibm.com>
On Tue, Feb 16, 2016 at 03:54:18PM +0100, Greg Kurz wrote:
> This series is a new tentative to have cleaner cross-endian code.
>
> Patches 1/3 is new: it fixes a side-effect in case vhost_init_used() fails.
>
> Patch 2/3 comes from v1: it renames cross-endian helpers
>
> Patch 3/3 is new: it simply renames vhost_init_used() as suggested by Michael.
Is this on top of my tree?
> ---
>
> Greg Kurz (3):
> vhost: fix error path in vhost_init_used()
> vhost: rename cross-endian helpers
> vhost: rename vhost_init_used()
>
>
> drivers/vhost/net.c | 2 +-
> drivers/vhost/scsi.c | 2 +-
> drivers/vhost/test.c | 2 +-
> drivers/vhost/vhost.c | 49 +++++++++++++++++++++++++++++++++++++------------
> drivers/vhost/vhost.h | 2 +-
> 5 files changed, 41 insertions(+), 16 deletions(-)
next prev parent reply other threads:[~2016-02-16 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 14:54 [PATCH v2 0/3] vhost: cross-endian code cleanup Greg Kurz
2016-02-16 14:54 ` Greg Kurz
2016-02-16 14:54 ` [PATCH v2 1/3] vhost: fix error path in vhost_init_used() Greg Kurz
2016-02-16 14:54 ` Greg Kurz
2016-02-16 14:59 ` [PATCH v2 2/3] vhost: rename cross-endian helpers Greg Kurz
2016-02-16 14:59 ` Greg Kurz
2016-02-16 14:59 ` [PATCH v2 3/3] vhost: rename vhost_init_used() Greg Kurz
2016-02-16 14:59 ` Greg Kurz
2016-02-16 15:34 ` Michael S. Tsirkin [this message]
2016-02-16 15:34 ` [PATCH v2 0/3] vhost: cross-endian code cleanup Michael S. Tsirkin
2016-02-16 15:43 ` Greg Kurz
2016-02-16 15:43 ` Greg Kurz
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=20160216153413.GA32554@redhat.com \
--to=mst@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.