From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, QEMU Trivial <qemu-trivial@nongnu.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] net: Mark the 'hubport' netdev as deprecated
Date: Wed, 20 Sep 2017 14:33:55 +0100 [thread overview]
Message-ID: <20170920133355.GB9947@redhat.com> (raw)
In-Reply-To: <5e647277-d688-071d-7def-bd8d57dd7e66@redhat.com>
On Wed, Sep 20, 2017 at 09:45:59AM +0200, Thomas Huth wrote:
> On 24.05.2017 10:04, Thomas Huth wrote:
> > The 'hubport' netdev is closely tied to the 'vlan' concept which
> > has been marked as deprecated in commit a2dbe1356faff3cb6 already.
> > Thus we should also mark the hubport netdevs as deprecated to make
> > the remaining users aware that they should not use this anymore.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > net/hub.c | 4 ++++
> > qemu-options.hx | 6 ++++--
> > 2 files changed, 8 insertions(+), 2 deletions(-)
Needs to include a update to the qemu-doc.texi "Deprecated features"
appendix
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, QEMU Trivial <qemu-trivial@nongnu.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] net: Mark the 'hubport' netdev as deprecated
Date: Wed, 20 Sep 2017 14:33:55 +0100 [thread overview]
Message-ID: <20170920133355.GB9947@redhat.com> (raw)
In-Reply-To: <5e647277-d688-071d-7def-bd8d57dd7e66@redhat.com>
On Wed, Sep 20, 2017 at 09:45:59AM +0200, Thomas Huth wrote:
> On 24.05.2017 10:04, Thomas Huth wrote:
> > The 'hubport' netdev is closely tied to the 'vlan' concept which
> > has been marked as deprecated in commit a2dbe1356faff3cb6 already.
> > Thus we should also mark the hubport netdevs as deprecated to make
> > the remaining users aware that they should not use this anymore.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > net/hub.c | 4 ++++
> > qemu-options.hx | 6 ++++--
> > 2 files changed, 8 insertions(+), 2 deletions(-)
Needs to include a update to the qemu-doc.texi "Deprecated features"
appendix
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-09-20 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:04 [Qemu-devel] [PATCH] net: Mark the 'hubport' netdev as deprecated Thomas Huth
2017-09-20 7:45 ` [Qemu-trivial] " Thomas Huth
2017-09-20 7:45 ` Thomas Huth
2017-09-20 11:07 ` [Qemu-trivial] " Paolo Bonzini
2017-09-20 11:07 ` Paolo Bonzini
2017-09-20 11:57 ` [Qemu-trivial] " Thomas Huth
2017-09-20 11:57 ` Thomas Huth
2017-09-20 16:50 ` [Qemu-trivial] " Paolo Bonzini
2017-09-20 16:50 ` Paolo Bonzini
2017-09-20 13:33 ` Daniel P. Berrange [this message]
2017-09-20 13:33 ` Daniel P. Berrange
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=20170920133355.GB9947@redhat.com \
--to=berrange@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.