Skip to content

mempolicy: go interface for set_mempolicy and get_mempolicy syscalls #514

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

Merged
merged 1 commit into from
Jun 9, 2025

Conversation

askervin
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@klihub klihub left a comment

Choose a reason for hiding this comment

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

Small nit. Otherwise looks good.

@klihub klihub requested a review from fmuyassarov May 26, 2025 17:12
Copy link
Collaborator

@klihub klihub left a comment

Choose a reason for hiding this comment

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

Is there any real benefit of not having this as (potentially separate commit but) part of #515 ?

@askervin
Copy link
Collaborator Author

Is there any real benefit of not having this as (potentially separate commit but) part of #515 ?

This commit is in a separate PR to limit the lines of code for easier review. So if there was a change that would be reasonable stand-alone change as is, I filed a separate PR. This is comparable to PR #513 that adds a function to an interface, yet there is no user for the function in the same PR.

@klihub klihub merged commit 81122e3 into containers:main Jun 9, 2025
8 checks passed
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