netdev - Re: [net-next 01/14] clarify implementation of ethtool's get_ts

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]

Date:	Fri, 17 Jul 2015 21:17:40 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Cc:	davem@...emloft.net, Jacob Keller <jacob.e.keller@...el.com>,
	netdev@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com,
	jogreene@...hat.com
Subject: Re: [net-next 01/14] clarify implementation of ethtool's get_ts_info
 op

On Fri, Jul 17, 2015 at 07:25:10AM -0700, Jeff Kirsher wrote:
> From: Jacob Keller <jacob.e.keller@...el.com>
> 
> This patch adds some clarification about the intended way to implement
> both SIOCSHWTSTAMP and ethtool's get_ts_info. The HWTSTAMP API has
> several Rx filters which are very specific, as well as more general
> filters. The specific filters really only exist to support some broken
> hardware which can't fully implement the generic filters. This patch
> adds clarification that it is okay to support the specific filters in
> SIOCSHWTSTAMP by upscaling them to the generic filters. In addition,
> update the header for ethtool_ts_info to specify that drivers ought to
> only report the filters they support without upscaling in this manner.

Acked-by: Richard Cochran <richardcochran@...il.com>

(for this patch and the other get_ts_info patches)
--
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