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

Question:blobmsg_add_u64() #3

Open
zhao-wuji-ahh opened this issue Aug 29, 2023 · 2 comments
Open

Question:blobmsg_add_u64() #3

zhao-wuji-ahh opened this issue Aug 29, 2023 · 2 comments

Comments

@zhao-wuji-ahh
Copy link

I want to know why the input parameters of the following functions are unsigned, why are they treated as signed?Could somebody help me?

blobmsg_add_u64(struct blob_buf *buf, const char *name, uint64_t val)
{
val = cpu_to_be64(val);
return blobmsg_add_field(buf, BLOBMSG_TYPE_INT64, name, &val, 8);
}

@zhao-wuji-ahh
Copy link
Author

why not create a new function to deal with signed parameters?

@zhao-wuji-ahh
Copy link
Author

@hauke @nbd168

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

No branches or pull requests

1 participant