From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Cochran Subject: Re: [PATCH] net: Improve SO_TIMESTAMPING documentation and fix a minor code bug Date: Wed, 5 Mar 2014 09:12:45 +0100 Message-ID: <20140305081245.GA4287@netboy> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: Andy Lutomirski Return-path: Received: from mail-ee0-f41.google.com ([74.125.83.41]:34100 "EHLO mail-ee0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750747AbaCEIM6 (ORCPT ); Wed, 5 Mar 2014 03:12:58 -0500 Received: by mail-ee0-f41.google.com with SMTP id t10so257680eei.28 for ; Wed, 05 Mar 2014 00:12:57 -0800 (PST) Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Tue, Mar 04, 2014 at 05:24:10PM -0800, Andy Lutomirski wrote: > The original documentation was very unclear. > > The code fix is presumably related to the formerly unclear > documentation: SOCK_TIMESTAMPING_RX_SOFTWARE has no effect on > __sock_recv_timestamp's behavior, so calling __sock_recv_ts_and_drops > from sock_recv_ts_and_drops if only SOCK_TIMESTAMPING_RX_SOFTWARE is > set is pointless. This should have no user-observable effect. > > Signed-off-by: Andy Lutomirski > --- Acked-by: Richard Cochran