Re: [libvirt] [PATCH 2/2] net: Drop the NetLegacy structure, always use Netdev instead

Thomas Huth writes: > Now that the "name" parameter is gone, there is hardly any difference > between NetLegacy and Netdev anymore. Drop NetLegacy and always use > Netdev to simplify the code quite a bit. > > Signed-off-by: Thomas Huth Took me a minute to see the actual difference. Here's

Re: [libvirt] [PATCH 2/2] net: Drop the NetLegacy structure, always use Netdev instead

On 06/12/2019 16.14, Eric Blake wrote: > On 12/5/19 11:36 PM, Thomas Huth wrote: >> Now that the "name" parameter is gone, there is hardly any difference >> between NetLegacy and Netdev anymore. Drop NetLegacy and always use >> Netdev to simplify the code quite a bit. >> >> Signed-off-by: Thomas

Re: [libvirt] [PATCH 2/2] net: Drop the NetLegacy structure, always use Netdev instead

On 12/5/19 11:36 PM, Thomas Huth wrote: Now that the "name" parameter is gone, there is hardly any difference between NetLegacy and Netdev anymore. Drop NetLegacy and always use Netdev to simplify the code quite a bit. Signed-off-by: Thomas Huth --- Initial focus on the QAPI change: +++

[libvirt] [PATCH 2/2] net: Drop the NetLegacy structure, always use Netdev instead

Now that the "name" parameter is gone, there is hardly any difference between NetLegacy and Netdev anymore. Drop NetLegacy and always use Netdev to simplify the code quite a bit. Signed-off-by: Thomas Huth --- net/net.c | 74 --- qapi/net.json