From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: sw@weilnetz.de, aliguori@us.ibm.com,
Corey Bryant <coreyb@linux.vnet.ibm.com>,
rmarwah@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] Change "-net tap, helper" to "-net tap, bridgehelper"
Date: Wed, 8 Feb 2012 23:42:56 +0000 [thread overview]
Message-ID: <201202082342.57354.paul@codesourcery.com> (raw)
In-Reply-To: <1328577371-19939-1-git-send-email-coreyb@linux.vnet.ibm.com>
> The purpose of the "helper" option for "-net tap" isn't obvious
> based on its name. This patch changes the option name to
> "bridgehelper" to make its purpose more self-documenting.
>
> With this patch, a typical invocation will be similar to one of the
> following (where the default bridge is br0):
I don't see why this option is specific to bridging. Surely it could be used
in any system where you want to have a helper script open the tap device.
Paul
prev parent reply other threads:[~2012-02-08 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 1:16 [Qemu-devel] [PATCH] Change "-net tap, helper" to "-net tap, bridgehelper" Corey Bryant
2012-02-08 23:42 ` Paul Brook [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=201202082342.57354.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rmarwah@linux.vnet.ibm.com \
--cc=sw@weilnetz.de \
/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).