> -----Original Message----- > From: Premkumar Jonnala > Sent: Monday, November 16, 2015 11:42 AM > To: 'David Miller'; [email protected] > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected] > Subject: RE: [PATCH] bonding: Offloading bonds to hardware > > > > > -----Original Message----- > > From: David Miller [mailto:[email protected]] > > Sent: Saturday, November 14, 2015 12:40 AM > > To: [email protected] > > Cc: Premkumar Jonnala; [email protected]; [email protected]; > > [email protected]; [email protected]; [email protected]; > > [email protected] > > Subject: Re: [PATCH] bonding: Offloading bonds to hardware > > > > From: Florian Fainelli <[email protected]> > > 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. > > Thank you for the feedback David. I am currently handling/implementing > these notifications in a custom (closed source) driver. I will update the > diff > with an actual demo of the handler, and resend the diffs.
Clarification: When I say a "closed source" driver, I was implying a closed-source user-level application that programs hardware. Thanks Prem > > Thanks > Prem -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
