From: Yuval Mintz <yuval.mi...@qlogic.com> Date: Mon, 18 Apr 2016 03:59:42 +0000
> The third option I see is to completely ditch this, stating that although > We obviously CAN set the non-volatile memory we CAN'T do it with the > regular API, and to move into doing this via some proprietary API such > as debugfs. Why go to debugfs rather than gracefully extending the ethtool stuff to explicitly support what you need? Anyone who says debugfs just isn't willing to design things correctly. That's why I basically have started rejecting everything that tries to use debugfs in the networking, it's the "I'm too damn lazy to do this properly" option and I simply won't stand for crap like that any more.