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

drivers: espi: mchp: Report correct length during OOB Rx operation #25105

Merged
merged 1 commit into from
May 9, 2020

Conversation

albertofloyd
Copy link
Collaborator

Use correct HAL macro to report correct amount of bytes received during OOB Rx operation.

Fixes #25091
Depends on #24945

Use correct HAL macro to report amount of bytes received.

Signed-off-by: Jose Alberto Meza <jose.a.meza.arellano@intel.com>
@andrewboie andrewboie added the Trivial Changes that can be reviewed by anyone, i.e. doc changes, minor build system tweaks, etc. label May 7, 2020
@andrewboie
Copy link
Contributor

This needs #24945 merged first? that PR is having shippable issues

@albertofloyd albertofloyd requested a review from andrewboie May 8, 2020 01:20
@albertofloyd
Copy link
Collaborator Author

This needs #24945 merged first? that PR is having shippable issues

#24945 has been corrected by @scottwcpg.

@andrewboie andrewboie added the DNM This PR should not be merged (Do Not Merge) label May 8, 2020
@andrewboie
Copy link
Contributor

Putting DNM on this, #24945 needs to go in first, and that PR is still in-flight

@nashif nashif removed the DNM This PR should not be merged (Do Not Merge) label May 9, 2020
@nashif nashif merged commit eaaf1af into zephyrproject-rtos:master May 9, 2020
@albertofloyd albertofloyd deleted the espi_oob_len_fix branch May 12, 2020 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Trivial Changes that can be reviewed by anyone, i.e. doc changes, minor build system tweaks, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

drivers: eSPI: Incorrect handling of OOB registers leads to report wrong OOB packet len
5 participants