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

No-op on s390x #556

Merged
merged 2 commits into from
Nov 2, 2023
Merged

No-op on s390x #556

merged 2 commits into from
Nov 2, 2023

Conversation

cgwalters
Copy link
Member

Closes: #550

I believe we don't have anything to do here; zipl always merges kernel/initramfs/bootloader and hence s390x updates are owned by ostree effectively.

This is part of being a no-op on s390x.
Nothing to do there.
@cgwalters
Copy link
Member Author

cc @nikita-dubrovskii

Copy link
Member

@jmarrero jmarrero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@cgwalters cgwalters merged commit 22c714c into coreos:main Nov 2, 2023
8 checks passed
@nikita-dubrovskii
Copy link

Yes, ostree with its zipl wraper handles BLS either automatically, or with extra logic in SecEx case

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.

add s390x support
3 participants