From: Alex Williamson <alex.williamson@hp.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Mark McLoughlin <markmc@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH 3/5][RFC] virtio-net: Name the status bits, adding promisc and allmulti
Date: Wed, 07 Jan 2009 11:14:17 -0700 [thread overview]
Message-ID: <1231352057.7109.132.camel@lappy> (raw)
In-Reply-To: <4964EFE6.2060209@codemonkey.ws>
On Wed, 2009-01-07 at 12:09 -0600, Anthony Liguori wrote:
> Alex Williamson wrote:
> > virtio-net: Name the status bits, adding promisc and allmulti
> >
>
> I'd prefer the use of #define's like we have today. bit fields have
> really weird packing and ordering properties across architectures.
Ok, it made a few things easier, but I'll work on using a mask
interface. Thanks,
Alex
--
Alex Williamson HP Open Source & Linux Org.
prev parent reply other threads:[~2009-01-07 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 17:37 [Qemu-devel] [PATCH 3/5][RFC] virtio-net: Name the status bits, adding promisc and allmulti Alex Williamson
2009-01-07 18:09 ` [Qemu-devel] " Anthony Liguori
2009-01-07 18:14 ` Alex Williamson [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=1231352057.7109.132.camel@lappy \
--to=alex.williamson@hp.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.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).