pldm-file: client: send NEXT_PART requests with TransferContext set#35
Merged
mkj merged 1 commit intoCodeConstruct:mainfrom Sep 25, 2025
Merged
pldm-file: client: send NEXT_PART requests with TransferContext set#35mkj merged 1 commit intoCodeConstruct:mainfrom
mkj merged 1 commit intoCodeConstruct:mainfrom
Conversation
Currently, we clear out the TransferContext field of NEXT_PART multipart receive commands, in line with handling for the offset and length fields (as required by the spec). However, hosts may be relying on the TransferContext for subsequent requests too, so don't clear that out for NEXT_PART reqs. Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Member
|
Thanks. The PLDM File DSP0242 example sequence diagrams make it clear that TransferContext=FileDescriptor is set for subsequent requests. |
Member
Author
|
Ah, good point. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently, we clear out the TransferContext field of NEXT_PART multipart receive commands, in line with handling for the offset and length fields (as required by the spec). However, hosts may be relying on the TransferContext for subsequent requests too, so don't clear that out for NEXT_PART reqs.