dkms: Use a generic missing kernel headers error message#594
Merged
scaronni merged 1 commit intoJul 13, 2026
Conversation
Member
|
True, but I would remove the mention completely about the speciific debian package and just use a generic sentence:
|
Avoid suggesting distro-specific package names such as linux-headers-<version> or kernel-devel-<version>, since package naming differs across distributions. Point users to their distribution's matching kernel headers package, or --kernelsourcedir. Signed-off-by: Hadi Hbus <hhbus@nvidia.com>
HadiHbus
force-pushed
the
fix-rpm-kernel-devel-message
branch
from
fd2374c to
cb6297f
Compare
HadiHbus
changed the title
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.
The missing kernel headers error only suggested the Debian-style linux-headers package.
Add the rpm-based kernel-devel package to make the DKMS guidance useful across packaging ecosystems, and update the expected test output accordingly.