qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Shaun Reitan <shaun.reitan@ndchost.com>, qemu-devel@nongnu.org
Cc: Eric Blake <eblake@redhat.com>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Add ability to provide ifname when using netdev bridge or tap helper
Date: Wed, 17 Jan 2018 11:35:00 +0800	[thread overview]
Message-ID: <78acb30d-ac20-4a59-50dc-9a247e190314@redhat.com> (raw)
In-Reply-To: <20180116231824.27114-1-shaun.reitan@ndchost.com>



On 2018年01月17日 07:18, Shaun Reitan wrote:
> This patch replaces the patch I sent yesturday. This one fixes
> a bug in my original code as well as corrects a few styling
> issues. Hopfully this one comes out correct!  Sorry for the
> inconvienece.
>   
> When currently using -netdev bridge or -netdev tap with a helper
> you are unable to set an ifname. This patch adds that ability so
> that you can now specify an ifname.
>
> Signed-off-by: Shaun Reitan <shaun.reitan@ndchost.com>
> ---
>   net/tap.c            | 33 ++++++++++++++++++++++++---------
>   qapi/net.json        |  1 +
>   qemu-bridge-helper.c | 11 +++++++++--
>   qemu-options.hx      |  2 +-
>   4 files changed, 35 insertions(+), 12 deletions(-)
>

Applied.

Thanks

  reply	other threads:[~2018-01-17  3:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 23:18 [Qemu-devel] [PATCH] Add ability to provide ifname when using netdev bridge or tap helper Shaun Reitan
2018-01-17  3:35 ` Jason Wang [this message]
2018-01-17 10:31 ` Daniel P. Berrange
2018-01-17 10:39   ` Paolo Bonzini
2018-01-17 13:28     ` Philippe Mathieu-Daudé
2018-01-17 10:53   ` Jason Wang
2018-01-17 10:58     ` Daniel P. Berrange
2018-01-17 15:26 ` Eric Blake
2018-01-17 18:11   ` Shaun Reitan
2018-01-18 11:53     ` Jason Wang
2018-01-18 21:56       ` Shaun Reitan

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=78acb30d-ac20-4a59-50dc-9a247e190314@redhat.com \
    --to=jasowang@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shaun.reitan@ndchost.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).