[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090805.201937.242694288.davem@davemloft.net>
Date: Wed, 05 Aug 2009 20:19:37 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dbaryshkov@...il.com
Cc: netdev@...r.kernel.org, slapin@...fans.org,
linux-zigbee-devel@...ts.sourceforge.net
Subject: Re: [PATCH 2/3] af_ieee802154: provide dummy get/setsockopt
From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Date: Thu, 6 Aug 2009 01:41:39 +0400
> On Wed, Aug 05, 2009 at 12:17:14PM -0700, David Miller wrote:
>> From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
>> 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 <dbaryshkov@...il.com>
>>
>> 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.
Ok, my bad. The patch is fine.
--
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
Powered by blists - more mailing lists