New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can i backport new zstd kernel module to Linux 4.x? #3188
Comments
If you're porting to a release older than Its a bit different now but basically look for duplicates, and only add them to |
Thanks! I'm working on Linux 4.9, which is much older than 4.17. Before this, I used a dirty trick to avoid this problem, but it doesn't seem to work. You can see my changes at urain39/android_kernel_meizu_m1721@2561c1e The main problem is that I get a kernel panic after changing: dmesg-ramoops-0
Since this is a custom Linux kernel, I can't identify the immediate cause, I'll test with mainline 4.9 when I have time (it may take a bit long time). |
Sorry, this is my mistake. This issue (kernel panic) is caused by |
I am doing the backport of zstd-1.4.10+ for Linux 4.x, but I have encountered some problems.
The output shows that the problem exists only in common/*.
I checked the code for the mainline kernel and found that these issues seem to be caused by build script changes.
(changes built-in.o -> built-in.a)
The text was updated successfully, but these errors were encountered: