Skip to content

Cellular: Initialize CellularContext member variables in correct class #10557

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

Merged
merged 1 commit into from
May 15, 2019

Conversation

jarvte
Copy link
Contributor

@jarvte jarvte commented May 10, 2019

Description

CellularContext member variables were initialized in inheriting class.
Now in base class where they should be initialized so that every inheriting
class don't have to init them.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@AnttiKauppila

Release Notes

CellularContext member variables were initialized in inheriting class.
Now in base class where they should be initialized so that every inheriting
class don't have to init them.
@ciarmcom ciarmcom requested review from AnttiKauppila and a team May 10, 2019 09:00
@ciarmcom
Copy link
Member

@jarvte, thank you for your changes.
@AnttiKauppila @ARMmbed/mbed-os-wan @ARMmbed/mbed-os-maintainers please review.

@@ -19,6 +19,15 @@

namespace mbed {

CellularContext::CellularContext() : _next(0), _stack(0), _pdp_type(DEFAULT_PDP_TYPE),

Choose a reason for hiding this comment

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

Should be inited in the same order as declared in header?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, and they are what I can tell. Please tell which are not in correct order.

@0xc0170
Copy link
Contributor

0xc0170 commented May 13, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented May 13, 2019

Test run: FAILED

Summary: 1 of 7 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_build-ARM

@0xc0170
Copy link
Contributor

0xc0170 commented May 14, 2019

CI restarted

@mbed-ci
Copy link

mbed-ci commented May 14, 2019

Test run: FAILED

Summary: 1 of 11 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_cloud-client-test

@adbridge
Copy link
Contributor

There is something strange, conflict wise, with both this and the related 10554 and neither will patch across to 5.12. Thus bumping to 5.13.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants