realtek-rtl8195am-wifi-headerfile-updates

[M-ichae-l]

Description

1. add "extern "C" {} " to "wifi_ind.h" for being called by CPP files.
2. fix for Unable to register for wifi status updates with Realtek 8195 #8481

Pull request type

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

[adbridge]

@M-ichae-l Please note that the description template guidelines says not to edit the template in any way other than to add your description and add one X to one of the types. You have removed all the other types and thus modified the template. Can you please fix this.

[M-ichae-l]

@adbridge
I have updated. If it is still not the requirements, do we have a way to revert all the changes in the Description?

[0xc0170]

If you click on edited above the comment, you can find the history there.

Thanks for the update, LGTM

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3661
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8750/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 3267
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8750/

[NirSonnenschein]

re-test to see if CI is more responsive
/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3662
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8750/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 3269
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8750/

[0xc0170]

Info: This PR has been re-bundled into a new rollup PR (#8800).

No further work is needed here, as once that PR is merged, this PR will also be closed and marked as merged.
If any more commits are made in this PR, this PR will remain open and have to go through CI on its own.

[samchuarm]

Hi , since PR #8800 got closed, how do we proceed with this PR to fix issue #8481 ? Thanks.

[0xc0170]

Hi , since PR #8800 got closed, how do we proceed with this PR to fix issue #8481 ? Thanks.

I am on it. I might create a new rollup soon. Some PR from 8800 are ready for merge.

[0xc0170]

Info: This PR has been re-bundled into a new rollup PR (#8838 ).

No further work is needed here, as once that PR is merged, this PR will also be closed and marked as merged.
If any more commits are made in this PR, this PR will remain open and have to go through CI on its own.