[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56BC9B48.5080708@redhat.com>
Date: Thu, 11 Feb 2016 15:31:36 +0100
From: Ivan Vecera <ivecera@...hat.com>
To: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, idosch@...lanox.com, eladr@...lanox.com,
yotamg@...lanox.com, ogerlitz@...lanox.com, yishaih@...lanox.com,
dledford@...hat.com, sean.hefty@...el.com,
hal.rosenstock@...il.com, eugenia@...lanox.com,
roopa@...ulusnetworks.com, nikolay@...ulusnetworks.com,
hadarh@...lanox.com, jhs@...atatu.com, john.fastabend@...il.com,
jeffrey.t.kirsher@...el.com, jbenc@...hat.com
Subject: Re: [patch net-next RFC 1/6] Introduce devlink infrastructure
On 3.2.2016 11:47, Jiri Pirko wrote:
> +struct devlink_ops {
> + size_t priv_size;
> + int (*port_type_set)(struct devlink_port *devlink_port,
> + enum devlink_port_type port_type);
> +};
It does not make sense to have priv_size member here... If it is
necessary it should be placed in struct devlink.
Ivan
Powered by blists - more mailing lists