[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YlBX5lhYHIXE0oBK@kroah.com>
Date: Fri, 8 Apr 2022 17:42:30 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: Sasha Levin <sashal@...nel.org>, stable <stable@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Soheil Hassas Yeganeh <soheil@...gle.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Paolo Abeni <pabeni@...hat.com>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH stable 0/3] SOF_TIMESTAMPING_OPT_ID backport to 4.14 and
4.19
On Fri, Apr 08, 2022 at 03:29:30PM +0000, Vladimir Oltean wrote:
> Hello Greg, Sasha,
>
> On Wed, Apr 06, 2022 at 10:29:53PM +0300, Vladimir Oltean wrote:
> > As discussed with Willem here:
> > https://lore.kernel.org/netdev/CA+FuTSdQ57O6RWj_Lenmu_Vd3NEX9xMzMYkB0C3rKMzGgcPc6A@mail.gmail.com/T/
> >
> > the kernel silently doesn't act upon the SOF_TIMESTAMPING_OPT_ID socket
> > option in several cases on older kernels, yet user space has no way to
> > find out about this, practically resulting in broken functionality.
> >
> > This patch set backports the support towards linux-4.14.y and linux-4.19.y,
> > which fixes the issue described above by simply making the kernel act
> > upon SOF_TIMESTAMPING_OPT_ID as expected.
> >
> > Testing was done with the most recent (not the vintage-correct one)
> > kselftest script at:
> > tools/testing/selftests/networking/timestamping/txtimestamp.sh
> > with the message "OK. All tests passed".
>
> Could you please pick up these backports for "stable"? Thanks.
You sent this 2 days ago!
Please relax :)
Powered by blists - more mailing lists