This repository has been archived by the owner on Nov 14, 2024. It is now read-only.
[nrf noup] zephyr: Fix sending unsolicited disconnect result #140
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixup! [nrf noup] Monitor supplicant state and inform applications If STA is not connected but still disassociated for some reason e.g., wrong password, sending disconnect results is not intuitive as we have never sent connected status up, so, instead just send connect result with the reason code for failure. Fixes SHEL-2265. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
krish2718
requested review from
jukkar,
rado17,
sachinthegreen and
rlubos
as code owners
rado17
approved these changes
Dec 8, 2023
sachinthegreen
approved these changes
Dec 8, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixup! [nrf noup] Monitor supplicant state and inform applications
If STA is not connected but still disassociated for some reason e.g., wrong password, sending disconnect results is not intuitive as we have never sent connected status up, so, instead just send connect result with the reason code for failure.
Fixes SHEL-2265.