netdev - Re: [PATCH] net: 8021q: additionally pass SIOCSHWTSTAMP ioctl flag to, the real device

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] [day] [month] [year] [list]

Message-Id: <20150319.145036.2014651675915638641.davem@davemloft.net>
Date:	Thu, 19 Mar 2015 14:50:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	martin.gerbershagen@...ia.com
Cc:	kaber@...sh.net, netdev@...r.kernel.org
Subject: Re: [PATCH] net: 8021q: additionally pass SIOCSHWTSTAMP ioctl flag
 to, the real device

From: Martin Gerbershagen <martin.gerbershagen@...ia.com>
Date: Thu, 19 Mar 2015 11:08:36 +0100

> 
>    If vlan devices were used, hardware timestamping did not work. The
>    problem was that the SIOCSHWTSTAMP ioctl flag was not passed to the real
>    device. This is fixed with this patch.
> 
>    Signed-off-by: Martin Gerbershagen <martin.gerbershagen@...ia.com>

Please only submit patches against current sources.

Not only is the SIOCSHWTSTAMP there in vlan_dev_ioctl() already, unlike
your patch SIOCGHWTSTAMP is handled and passed down as well.

In fact it's been that way since 3.17 which was released in October 2014,
that's 5 months ago.

You want everyone reading your patch posting to care enough to review
it properly and integrate it if it is valid, yet you don't care enough
about your own change and the time invested by the developers here
reviewing your work to base your work againt current sources?
--
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