Fpgamatt/subdevid 0001 opae cfg #3125
Merged
Conversation
This file contains 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
Fix the opae.cfg entries for the jtag only PCI card, subdevice id 0x0001. Signed-off-by: Matthew Gerlach <matthew.gerlach@linux.intel.com>
Pull Request Test Coverage Report for Build 9214671944Details
💛 - Coveralls |
pcolberg
reviewed
May 23, 2024
CMakeLists.txt
Outdated
| @@ -956,7 +956,7 @@ else() | |||
| set(CPACK_PACKAGE_VERSION_PATCH "${OPAE_VERSION_REVISION}") | |||
| endif() | |||
| set(CPACK_PACKAGE_VERSION ${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MINOR}.${CPACK_PACKAGE_VERSION_PATCH}) | |||
| set(CPACK_PACKAGE_RELEASE 1) | |||
| set(CPACK_PACKAGE_RELEASE 6) | |||
There was a problem hiding this comment.
The release should be bumped on the release branch only.
fpgamatt
force-pushed
the
fpgamatt/subdevid-0001-opae-cfg
branch
from
803ba6e
to
685f972
Compare
pcolberg
reviewed
May 23, 2024
pcolberg
approved these changes
May 23, 2024
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.
PR Title should start with one of the following tags: [Fix]/[Feature]/[Style]/[Update]
[Fix]- Bug Fix
[Feature]- for new feature
[Style]- Grammar or branding fix
[Update]-For an update to an existing feature
------------- Keep everything below this line -------------------------
Description
Describe the issue, update, change or fix and why
Collateral (docs, reports, design examples, case IDs):
Tests added:
Tests run: