RPM: Explicitly set the required min/max kernel version for the DKMS #12146
Conversation
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
…package Signed-off-by: Armin Wehrfritz <[email protected]>
|
@awehrfritz I've included this in 2.1.0-rc6. |
Great, thanks! |
tonyhutter
approved these changes
Jun 1, 2021
behlendorf
approved these changes
Jun 1, 2021
|
Great, thanks for merging this! @tonyhutter, from the commit log in this branch, I gather that the 5.12 compatibility patches are backported to this branch. However, the META file still lists 5.11 as the maximum kernel version supported. Are there still some patches missing or is this an oversight? |
|
@awehrfritz I actually just put out a PR for zfs-2.0.5 today, which includes the META update: #12182 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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, context and description as in: #12124
@tonyhutter: I would appreciate if we could include this patch in the stable releases as well. This should do the trick for the 2.0.x series, I am not sure though how to get this into the 2.1.0 release as there is no staging branch.