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

Nitpicks #603

Merged
merged 2 commits into from
Dec 20, 2023
Merged

Nitpicks #603

merged 2 commits into from
Dec 20, 2023

Conversation

gperciva
Copy link
Member

No description provided.

crypto_compat.c spelling fix for:
    2023-10-14 crypto_compat_free(): handle recent OpenSSL and LibreSSL
    e5df014

Some mismatches between argument names in the declarations and
definitions:

tsnetwork.c, introduced in:
    2008-04-25 Tarsnap 1.0.0
    41f175d

crypto_compat.c, introduced in:
    2017-03-13 crypto_compat: begin, add crypto_compat_RSA_valid_size()
    d06e404

The header files uses `key`, as do all the other functions in this file.

Reported by:	clang-tidy
@@ -43,7 +43,7 @@ struct network_buf_cookie {
int flags;
};

static int callback_buf(void * cookie, int timedout);
static int callback_buf(void * cookie, int status);
Copy link
Member Author

Choose a reason for hiding this comment

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

This function is defined on line 57 (just a few lines down) with that arg being status, and that name seems a better match for how that arg is being used.

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, timedout is a historical name for that variable. I switched to status a long time ago but I guess I missed this one.

@cperciva cperciva merged commit f4560d8 into master Dec 20, 2023
2 checks passed
@gperciva gperciva deleted the nitpicks branch December 21, 2023 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants