[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160223.131657.1586772724014887499.davem@davemloft.net>
Date: Tue, 23 Feb 2016 13:16:57 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: hannes@...essinduktion.org, netdev@...r.kernel.org,
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,
brouer@...hat.com, ivecera@...hat.com, rami.rosen@...el.com
Subject: Re: [patch net-next 3/9] mlx4: Implement port type setting via
devlink interface
From: Jiri Pirko <jiri@...nulli.us>
Date: Tue, 23 Feb 2016 13:21:10 +0100
> Sysfs is not the place to do this things.
+1
> It was already discussed here multiple times. There was and attempt
> to use configfs, which was also refused. Netlink is the only place
> to go. For multiple reasons, including well defined api and
> behaviour, notifications, etc.
+1
Powered by blists - more mailing lists