From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: jasowang@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, akong@redhat.com
Subject: Re: [PATCH] virtio: don't expose u16 in userspace api
Date: Sun, 05 May 2013 16:58:25 -0400 (EDT) [thread overview]
Message-ID: <20130505.165825.1787385657172692387.davem@davemloft.net> (raw)
In-Reply-To: <20130503174941.043d10b7@nehalam.linuxnetplumber.net>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri, 3 May 2013 17:49:41 -0700
> Programs using virtio headers outside of kernel will no longer
> build because u16 type does not exist in userspace. All user ABI
> must use __u16 typedef instead.
>
> Bug introduce by:
> commit 986a4f4d452dec004697f667439d27c3fda9c928
> Author: Jason Wang <jasowang@redhat.com>
> Date: Fri Dec 7 07:04:56 2012 +0000
>
> virtio_net: multiqueue support
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Applied and queued up for -stable.
prev parent reply other threads:[~2013-05-05 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 0:49 [PATCH] virtio: don't expose u16 in userspace api Stephen Hemminger
2013-05-05 20:58 ` David Miller [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=20130505.165825.1787385657172692387.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akong@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).