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

capi: Enable unsafe_op_in_unsafe_fn lint #506

Merged
merged 1 commit into from
Jan 30, 2024
Merged

capi: Enable unsafe_op_in_unsafe_fn lint #506

merged 1 commit into from
Jan 30, 2024

Conversation

danielocfb
Copy link
Collaborator

Enable the unsafe_op_in_unsafe_fn lint. Refer to commit 0f4b25d ("Make unsafe blocks explicit") for details.

Enable the `unsafe_op_in_unsafe_fn` lint. Refer to commit 0f4b25d
("Make unsafe blocks explicit") for details.

Signed-off-by: Daniel Müller <deso@posteo.net>
Copy link

codecov bot commented Jan 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (07fdf1c) 93.53% compared to head (d064dce) 93.53%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #506   +/-   ##
=======================================
  Coverage   93.53%   93.53%           
=======================================
  Files          45       45           
  Lines        7980     7980           
=======================================
  Hits         7464     7464           
  Misses        516      516           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@danielocfb danielocfb merged commit c51d478 into libbpf:main Jan 30, 2024
31 checks passed
@danielocfb danielocfb deleted the topic/unsafe_op_in_unsafe_fn branch January 30, 2024 23:56
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