From: David Miller <davem@davemloft.net>
To: richard@arachsys.com, chris@arachsys.com
Cc: netdev@vger.kernel.org, jasowang@redhat.com,
qemu-devel@nongnu.org, arnd@arndb.de, mst@redhat.com
Subject: Re: [Qemu-devel] Macvtap bug: contractor wanted
Date: Wed, 19 Sep 2012 13:54:31 -0400 (EDT) [thread overview]
Message-ID: <20120919.135431.120723976574630277.davem@davemloft.net> (raw)
In-Reply-To: <20120919151133.GA23987@arachsys.com>
Solicitation of paid services or employment is absolutely not
appropriate on the vger.kernel.org mailing lists.
Please do not do this ever again.
next prev parent reply other threads:[~2012-09-19 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 9:20 [Qemu-devel] Slow inbound traffic on macvtap interfaces Chris Webb
2012-08-16 11:42 ` Michael S. Tsirkin
2012-08-16 14:27 ` Chris Webb
2012-08-16 15:36 ` Michael S. Tsirkin
2012-09-19 15:11 ` [Qemu-devel] Macvtap bug: contractor wanted Richard Davies, Chris Webb
2012-09-19 17:54 ` David Miller [this message]
2012-08-29 17:52 ` [Qemu-devel] Slow inbound traffic on macvtap interfaces Chris Webb
2012-08-30 8:20 ` Richard Davies
2012-08-30 8:44 ` Michael S. Tsirkin
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=20120919.135431.120723976574630277.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=chris@arachsys.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=richard@arachsys.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).