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

[feature-wisun] Corrected nanostack coverity warnings #14146

Closed
wants to merge 1 commit into from
Closed

[feature-wisun] Corrected nanostack coverity warnings #14146

wants to merge 1 commit into from

Conversation

mikaleppanen
Copy link

Summary of changes

Corrected nanostack coverity warnings.

Impact of changes

None

Migration actions required

None

Documentation

None


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[X] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

@mikter @artokin


@ciarmcom
Copy link
Member

@mikaleppanen, thank you for your changes.
@mikter @artokin @ARMmbed/mbed-os-maintainers please review.

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 21, 2021

Please rebase to the latest wisun branch (travis fix already there)

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 27, 2021

@mikaleppanen Rebase?

@artokin
Copy link
Contributor

artokin commented Apr 14, 2021

These changes are already merged in to the feature-wisun branch as part of the baseline update made in #14526. This PR can be closed.

@mikaleppanen
Copy link
Author

Closing this.

@mikaleppanen mikaleppanen deleted the nano_coverity_corr branch April 14, 2021 09:25
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.

None yet

5 participants