From: Vladimir Oltean <olteanv@gmail.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Broken SOF_TIMESTAMPING_OPT_ID in linux-4.19.y and earlier stable branches
Date: Fri, 25 Mar 2022 16:05:58 +0200 [thread overview]
Message-ID: <20220325140558.qdxl25ggqhpztbjh@skbuf> (raw)
In-Reply-To: <CA+FuTSeJCZ1F3b9rrLpdcp6sbok8OXBA40jSmtxbJ7cnQayr+w@mail.gmail.com>
On Fri, Mar 25, 2022 at 09:48:41AM -0400, Willem de Bruijn wrote:
> > Do you have any particular concerns about sending this patch to the
> > linux-stable branches for 4.19, 4.14 and 4.9? From https://www.kernel.org/
> > I see those are the only stable branches left.
>
> The second patch does not apply cleanly to 4.14.y and even the first
> (one-liner) has a conflict on 4.9.y.
>
> It would be good to verify by running the expanded
> tools/testing/selftests/net/txtimestamp.c against the patched kernels
> first. That should serve as a good test whether the feature works on a
> kernel, re: that previous point.
>
> If you want to test and send the 4.19.y patch, please go ahead. Or I
> can do it, but it will take some time.
I think I do have a setup where I can test all 3 stable kernels.
I'll see if I can backport the SO_TIMESTAMPING fixes to them and
validate using the kernel selftest and my app. If I'm successful,
I'll attach the patchsets here for you to review, then send to stable if
you're okay, would that work?
next prev parent reply other threads:[~2022-03-25 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 21:39 Broken SOF_TIMESTAMPING_OPT_ID in linux-4.19.y and earlier stable branches Vladimir Oltean
2022-03-25 13:15 ` Willem de Bruijn
2022-03-25 13:37 ` Vladimir Oltean
2022-03-25 13:48 ` Willem de Bruijn
2022-03-25 14:05 ` Vladimir Oltean [this message]
2022-03-25 14:14 ` Willem de Bruijn
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=20220325140558.qdxl25ggqhpztbjh@skbuf \
--to=olteanv@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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