Skip to content

Conversation

hasnainvirk
Copy link
Contributor

Description

Socket ID is usually spitted out by the modem, however there are cases
when the modem is actully taken in as an input argument, e.g., in the
case of QUECTEL M26 modem. This minor knit clarifies that the
CellularSocket::id can be an input argument.

Pull request type

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

Reviewers

@blind-owl @AriParkkila @mirelachirica @AnttiKauppila

Release Notes

Copy link

@AriParkkila AriParkkila left a comment

Choose a reason for hiding this comment

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

I think the original comment tries to say that Socket ID must conform with modem's specification.

We probably want to refer only to 3GPP specs, and not to any specific modem (such as M26) at the generic AT implementation.

Socket ID is usually spitted out by the modem, however there are cases
when the modem is actully taken in as an input argument, e.g., in the
case of QUECTEL M26 modem. This minor knit clarifies that the
CellularSocket::id can be an input argument.
@hasnainvirk
Copy link
Contributor Author

@AriParkkila @mirelachirica The comment is rephrased. Please review again.

@ciarmcom
Copy link
Member

@hasnainvirk, thank you for your changes.
@AriParkkila @blind-owl @mirelachirica @AnttiKauppila @ARMmbed/mbed-os-wan @ARMmbed/mbed-os-maintainers please review.

@adbridge
Copy link
Contributor

ci started

@mbed-ci
Copy link

mbed-ci commented Apr 26, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 1
Build artifacts

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.

6 participants