On Fri, Oct 9, 2020 at 5:43 PM Willem de Bruijn wrote:
>
> On Fri, Oct 9, 2020 at 8:30 PM Deepa Dinamani wrote:
> >
> > On Fri, Oct 9, 2020 at 3:32 AM Christian Eggers wrote:
> > >
> > > The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
> > > so SOCK_TSTAMP_NEW will first b
On Fri, Oct 9, 2020 at 8:30 PM Deepa Dinamani wrote:
>
> On Fri, Oct 9, 2020 at 3:32 AM Christian Eggers wrote:
> >
> > The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
> > so SOCK_TSTAMP_NEW will first be set and than reset again. Additionally
> > move it out of the test f
On Fri, Oct 9, 2020 at 3:32 AM Christian Eggers wrote:
>
> The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
> so SOCK_TSTAMP_NEW will first be set and than reset again. Additionally
> move it out of the test for SOF_TIMESTAMPING_RX_SOFTWARE as this seems
> unrelated.
The SO
On Fri, Oct 9, 2020 at 6:32 AM Christian Eggers wrote:
>
> The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
> so SOCK_TSTAMP_NEW will first be set and than reset again. Additionally
> move it out of the test for SOF_TIMESTAMPING_RX_SOFTWARE as this seems
> unrelated.
>
> Thi
The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
so SOCK_TSTAMP_NEW will first be set and than reset again. Additionally
move it out of the test for SOF_TIMESTAMPING_RX_SOFTWARE as this seems
unrelated.
This problem happens on 32 bit platforms were the libc has already
switc
5 matches
Mail list logo