Support Linux 4.20
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 3/30 of 4 patches 0 repliesNew
- v2 posting 2/30 of 4 patches 0 repliesSuperseded
- v2 posting 1/30 of 4 patches 0 repliesSuperseded
Patches in v2 posting 3/3 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [Buildroot] [PATCH v2 0/4] Support Linux 4.20
Quoted 9 lines
Quoted 8 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
"Peter" == Peter Korsgaard <[email protected]> writes:
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hello,
Quoted 2 lines · Peter Korsgaard
With 2019.02 becoming our next LTS and 4.20 NOT a LTS release, I wonder if it would make sense to still default to 4.19.x instead of 4.20.x?
Quoted 7 lines
Quoted 4 lines
Yes, that probably make sense. But in this case, we would need to get in touch with the kernel folks to get the
net_tstamp.hfix in -stable. It has the Fixes: tag, but it still hasn't been backported to 4.19-stable.Ok. The last few 4.19.x releases did not contain any
net/fixes, perhaps that will fixed now the holidays are over.
This has indeed been fixed in 4.19.14. I have sent a patch to change our default linux / linux-headers version back to 4.19.x:
https://patchwork.ozlabs.org/patch/1022974/
Signature · 1 line
Bye, Peter Korsgaard