On Tue, 5 Jul 2016 16:30:35 +0800
Jing Liu <liuj...@linux.vnet.ibm.com> wrote:
> Dear Conny,
>
> On 07/05/2016 03:56 PM, Cornelia Huck wrote:
>
> > +
> > +static const TypeInfo virtual_css_bridge_info = {
> > + .name = TYPE_VIRTUAL_CSS_BRIDGE,
> > + .parent = TYPE_SYS_BUS_DEVICE,
> > + .instance_size = sizeof(SysBusDevice),
>
> So we do not use VirtualCssBridge macro which includes max_queue for 2.7?
> Just curious that in this way, how to deal with the compat for 2.6, 2.5 ...?
We don't have to deal with compat for code I have not included for
upstream yet.
(I have not yet made up my mind exactly on how we want to support the
maximum number of virtqueues as other transports while keeping
backwards compatibility.)
