Skip to content
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

[scarthgap] Migrate to use Linux kernel v6.11.0 in linux-fslc #1939

Closed
wants to merge 7 commits into from

Conversation

Livius90
Copy link
Contributor

@Livius90 Livius90 commented Sep 12, 2024

It was tested without any errors on the following boards:

  • i.MX7D Pico-Pi - work ✅
  • i.MX93 11x11 EVK - work ✅

To get and migrate the latest mainline kernel branch to linux-fslc repo:

    git clone --single-branch --branch 6.11.x+fslc https://github.com/Livius90/linux-fslc.git
    cd linux-fslc
    git remote add fslc-mirror https://github.com/Freescale/linux-fslc.git
    git push -u fslc-mirror

Notes:

@Livius90
Copy link
Contributor Author

In the next several days Linux kernel v6.11 stable release will be available. Please wait a little for the merging, i will try it also. It could be cool to get the latest v6.11 instead.

@otavio
Copy link
Member

otavio commented Sep 14, 2024

Sure, we can wait. Either way, first we need to send the update to the master branch and later we do the backport.

@Livius90 Livius90 changed the title [scarthgap] Migrate to use Linux kernel v6.10.10 in linux-fslc [scarthgap] Migrate to use Linux kernel v6.11.0 in linux-fslc Sep 15, 2024
@Livius90
Copy link
Contributor Author

@otavio

Linux kernel v6.11 was tested without any errors on the following boards:

  • i.MX7D Pico-Pi - work ✅
  • i.MX93 11x11 EVK - work ✅

It is ready to use in linux-fslc.

@otavio
Copy link
Member

otavio commented Sep 26, 2024

I apologize to take longer to review this, and to be completely honest, I ended forgetting about this pull request.

I prepared the branch in the main repository with your respective branch. Is it possible for you to prepare the update to the master branch and then we apply it before merging this one?

Once you send the new pull request, I will merge it and then we do a rebase on this one on top of the current branch and then we can merge it directly.

@Livius90
Copy link
Contributor Author

Yes i can make a new pull request for master. But cryptodev-module need a patch fix just for scarthgap to able to use v6.11.x in scarthgap also. It can be a separated cryptodev PR also later only for scarthgap.

@Livius90 Livius90 closed this Sep 27, 2024
@Livius90 Livius90 deleted the scarthgap branch September 27, 2024 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants