Re: [patch net-next 1/9] Introduce devlink infrastructure

2016-02-24 Thread Jiri Pirko
Wed, Feb 24, 2016 at 08:02:32AM CET, yuval.mi...@qlogic.com wrote: >> + * An overall lock guarding every operation comming from userspace. >> + * If also guards devlink devices list and it is taken when >> + * driver registers/unregisters it. >Several typos in comment. Already fixed in v2. > >>

RE: [patch net-next 1/9] Introduce devlink infrastructure

2016-02-23 Thread Yuval Mintz
> + * An overall lock guarding every operation comming from userspace. > + * If also guards devlink devices list and it is taken when > + * driver registers/unregisters it. Several typos in comment. > +static void devlink_notify(struct devlink *devlink, enum > +devlink_command cmd) { ... > +

Re: [patch net-next 1/9] Introduce devlink infrastructure

2016-02-22 Thread Jiri Pirko
Mon, Feb 22, 2016 at 11:29:06PM CET, ro...@cumulusnetworks.com wrote: >On 2/22/16, 10:31 AM, Jiri Pirko wrote: >> From: Jiri Pirko >> >> Introduce devlink infrastructure for drivers to register and expose to >> userspace via generic Netlink interface. >> >> There are two basic

Re: [patch net-next 1/9] Introduce devlink infrastructure

2016-02-22 Thread roopa
On 2/22/16, 10:31 AM, Jiri Pirko wrote: > From: Jiri Pirko > > Introduce devlink infrastructure for drivers to register and expose to > userspace via generic Netlink interface. > > There are two basic objects defined: > devlink - one instance for every "parent device", for

[patch net-next 1/9] Introduce devlink infrastructure

2016-02-22 Thread Jiri Pirko
From: Jiri Pirko Introduce devlink infrastructure for drivers to register and expose to userspace via generic Netlink interface. There are two basic objects defined: devlink - one instance for every "parent device", for example switch ASIC devlink port - one instance for