On Wed, Aug 05, 2009 at 12:17:14PM -0700, David Miller wrote: > From: Dmitry Eremin-Solenikov <[email protected]> > Date: Wed, 5 Aug 2009 11:28:16 +0400 > > > Provide dummt get/setsockopt implementations to stop these > > syscalls from oopsing on our sockets. > > > > Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> > > See "sock_no_getsockopt()" and "sock_no_setsockopt()" which are > provided specifically for this situation.
There functions are to be used in struct proto_ops and not in the struct proto. I'd like to use sock_common_get/setsockopt() from the beginning, as there will be sockopts at least for dgram protocols. If you say so, I can, of course, replace this patch with the one you suggested. However I really don't see a point in doing this. -- With best wishes Dmitry ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Linux-zigbee-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
