| commit | 4262e95c1c0a09c7f98ea6623d364bfda41e8bec | |
| author | Daniel Borkmann <dborkman@redhat.com> | |
| Sat, 16 Mar 2013 16:59:35 +0000 (16 17:59 +0100) | ||
| committer | Daniel Borkmann <dborkman@redhat.com> | |
| Sat, 16 Mar 2013 16:59:35 +0000 (16 17:59 +0100) | ||
| tree | 64309f7b022b5ed7e730d35589a221c6b336f026 | treesnapshot (tar.gz zip) |
| parent | 7a3b0f2226f7ad5f5ba20bcab5ef0f5c2b75e17d | commitdiff |
ring: don't care if we cannot active hw timestamping
Hw timestaming is currently done, if we have the header file from
the kernel available. If it fails, we currently bail out, which is
bullshit. Just returning is enough, since some users might have the
header available, but not a NIC supporting hw timestaming.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Hw timestaming is currently done, if we have the header file from
the kernel available. If it fails, we currently bail out, which is
bullshit. Just returning is enough, since some users might have the
header available, but not a NIC supporting hw timestaming.
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
| ring.h | diffblobblamehistory |