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

[master] linux-fslc: 6.6.50 -> 6.11.0 #1954

Merged
merged 3 commits into from
Sep 28, 2024
Merged

Conversation

Livius90
Copy link
Contributor

  • Update linux-fslc: 6.6.50 -> 6.11.0

@otavio
Copy link
Member

otavio commented Sep 27, 2024

Thank you for looking at this. Please keep the 6.6 kernel but rename it to LTS, as we did for the 6.1.

The 6.11 kernel should be a new recipe without the LTS suffix, so the flavor they choose is transparent to the user.

While you are on it, if you can update the 6.1 and 6.6 recipes to the latest version, that would be great. We can do the same when doing the backports. I have updated the respective branches in our repository.

@Livius90
Copy link
Contributor Author

@otavio
Do you like to keep linux-fslc-lts_6.1.bb also?

@otavio
Copy link
Member

otavio commented Sep 27, 2024

I think that for now it's important to keep as it is maintained and there might be users of it. Maybe when the next LTS is released, then we can drop it. What do you think?

@Livius90
Copy link
Contributor Author

Livius90 commented Sep 27, 2024

In master branch linux-fslc-lts_6.1.bb is useless for future, because now the latest official LTS is v6.6.x which available as an LTS, linux-fslc-lts_6.6.bb. To keep linux-fslc-lts_6.1.bb can be important only in scarthgap, because it is possible that somebody still use it in a released scarthgap layer.

https://www.kernel.org/

@otavio
Copy link
Member

otavio commented Sep 28, 2024

You have a valid point. So, move to 6.1 to 6.6 LTS in the master branch, and keep the 6.1 version when preparing the backport.

@Livius90
Copy link
Contributor Author

You have a valid point. So, move to 6.1 to 6.6 LTS in the master branch, and keep the 6.1 version when preparing the backport.

Done

@otavio otavio merged commit cfabecc into Freescale:master Sep 28, 2024
@otavio
Copy link
Member

otavio commented Sep 28, 2024

Please prepare the pull request for backporting and then we can remove this 6.1 here in master branch.

@Livius90
Copy link
Contributor Author

I think you can use the Backport CI action and it will generate this PR automatically.

Copy link

Successfully created backport PR #1956 for scarthgap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants