Question:blobmsg_add_u64()
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 32
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
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);
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the blobmsg_add_u64() definition and tracing its call to blobmsg_add_field(). Determine whether the signed treatment is intentional or needs clarification in the project documentation. Done means providing a clear explanation of the uint64_t parameter and BLOBMSG_TYPE_INT64 behavior, with any relevant documentation updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100