From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
stable <stable@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Soheil Hassas Yeganeh <soheil@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH stable 0/3] SOF_TIMESTAMPING_OPT_ID backport to 4.14 and 4.19
Date: Sat, 9 Apr 2022 12:09:12 -0400 [thread overview]
Message-ID: <YlGvqEM0zbDc7OpX@sashalap> (raw)
In-Reply-To: <YlBX5lhYHIXE0oBK@kroah.com>
On Fri, Apr 08, 2022 at 05:42:30PM +0200, Greg Kroah-Hartman wrote:
>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 :)
I've queued these up.
In general, we don't pick up new patches during -rc releases, which is
when you've sent this patchset and which is why sometimes it takes a few
days for stuff to go in.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-04-09 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 19:29 [PATCH stable 0/3] SOF_TIMESTAMPING_OPT_ID backport to 4.14 and 4.19 Vladimir Oltean
2022-04-06 19:29 ` [PATCH 4.14 1/2] ipv6: add missing tx timestamping on IPPROTO_RAW Vladimir Oltean
2022-04-06 19:45 ` Willem de Bruijn
2022-04-06 19:47 ` Vladimir Oltean
2022-04-06 21:57 ` Willem de Bruijn
2022-04-06 19:29 ` [PATCH 4.14 2/2] net: add missing SOF_TIMESTAMPING_OPT_ID support Vladimir Oltean
2022-04-06 19:48 ` Willem de Bruijn
2022-04-06 19:29 ` [PATCH 4.19 1/1] " Vladimir Oltean
2022-04-08 15:29 ` [PATCH stable 0/3] SOF_TIMESTAMPING_OPT_ID backport to 4.14 and 4.19 Vladimir Oltean
2022-04-08 15:42 ` Greg Kroah-Hartman
2022-04-09 16:09 ` Sasha Levin [this message]
2022-04-29 8:38 ` Greg Kroah-Hartman
2022-04-29 9:54 ` Vladimir Oltean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YlGvqEM0zbDc7OpX@sashalap \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=stable@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).