6.5-compat: BLK_STS_NEXUS is renamed to BLK_STS_RESV_CONFLICT #15059
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.
Motivation and Context
In Linux commit 7ba150834b840f6f5cdd07ca69a4ccf39df59a66 the
BLK_STS_NEXUS
macro was renamed toBLK_STS_RESV_CONFLICT
Description
I have added conditionally-compiled code to use
BLK_STS_RESV_CONFLICT
instead ofBLK_STS_NEXUS
if the former is found to be defined duringconfigure
. Additionalautoconf
tests have been added to look for it.How Has This Been Tested?
Built on 6.4.2, compiled on 6.5rc1 but other blocking changes in new kernel prevent full build from completing.
Types of changes
Checklist:
Signed-off-by
.