netdev - Re: [PATCH] bonding: Offloading bonds to hardware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20151113.141006.1048458234203733687.davem@davemloft.net>
Date:	Fri, 13 Nov 2015 14:10:06 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	f.fainelli@...il.com
Cc:	pjonnala@...adcom.com, netdev@...r.kernel.org, sfeldma@...il.com,
	jiri@...nulli.us, nikolay@...ulusnetworks.com, idosch@...lanox.com,
	gospo@...ulusnetworks.com
Subject: Re: [PATCH] bonding: Offloading bonds to hardware

From: Florian Fainelli <f.fainelli@...il.com>
Date: Fri, 13 Nov 2015 10:38:48 -0800

> This is a good explanation of why you want the changes, and how this is
> implemented in a system utilizing that, but this is not documenting why
> you are making these changes to the bonding code, nor how they are
> supposed to be used by an implementor driver, since there is no such
> user posted (yet?).

I am basically not even going to look at proposals for new device ops
that don't also show an actual user of the new interfaces.

That's not how we do development, and not providing a real example
user of a new set of interfaces makes it impossible to properly review
such changes.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html