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

Fix typos related to NVMinfo struct and GetMachineMemoryByType function #2434

Merged
merged 1 commit into from
Mar 20, 2020

Conversation

katarzyna-z
Copy link
Collaborator

Signed-off-by: Katarzyna Kujawa katarzyna.kujawa@intel.com

@k8s-ci-robot
Copy link
Collaborator

Hi @katarzyna-z. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@katarzyna-z katarzyna-z changed the title Fix typoes related to NVMinfo struct and GetMachineMemoryByType function Fix typos related to NVMinfo struct and GetMachineMemoryByType function Mar 19, 2020
Signed-off-by: Katarzyna Kujawa <katarzyna.kujawa@intel.com>
@katarzyna-z katarzyna-z force-pushed the kk-fix-type-nvm-info branch from 7b586de to 22a367d Compare March 19, 2020 08:33
@dashpole
Copy link
Collaborator

/ok-to-test

Copy link
Collaborator

@dashpole dashpole left a comment

Choose a reason for hiding this comment

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

lgtm

@dashpole dashpole merged commit fdeff47 into google:master Mar 20, 2020
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.

5 participants