Skip to content

merge in contributed DG-RDMA fixes into release-2.4.3

Aaron Olivarez requested to merge 3286-merge-in-contributed-dg-rdma-fixes-into-release-2-4-3 into release-2.4.3

What this MR does / why we need it:

The following issues and MRs have been addressed together and backport them into release-2.4.3 branch:

#3275 (closed) - !970 (closed), #3277 (closed) - !972 (closed), #3280 (closed) - !975 (closed), as well as remaining bits from !929 (closed)

Steps to complete before submitting MR:

  • I have read Contribution guidelines

  • I have ensured I have a changelog written in the imperative form that is meaningful and accurately summarizes the work done

  • I have added the release notes label if applicable (more information below)

  • I have ensured the workflow labels are up to date and will continue to do so up until this work is merged into develop

  • I have added a category, type, and target release label along with all other labels as need be

  • My branch is up to date with develop. If it is not, then I have ensured my work does not conflict with other work

  • I agree my bugfix MR does not include new features/enhancements

  • I represent that bugfixes have been locally tested against the most recent major.minor release in which the bug exists

  • (REVIEWER ONLY) I have thoroughly gone through the above steps to ensure that they have been followed

Release Notes

If introducing a change that warrants a release note entry, please add the ~"Release Notes" label and include the release notes in this section. These notes are used to compile the release notes for the target release during the release process. Release notes should be written with the end user as the target audience.

Changelog

Changelog entries are parsed from merge request descriptions and the template below must be followed. Changelog entries must be written in the imperative mood. If there are multiple categories, the categories must be comma separated. Multiple changelog entries must be on their own line, preferably using a bulleted list. Valid "types" correspond to our "type::" labels. Valid categories correspond to our "Category:" labels.

Template:
type(category[,category, ...]): write a short description

Example:

  • bug(runtime): Fix clock domain crossings in the time server
  • bug(hdl base): Add additional pipelining to DG-RDMA infrastructure
  • enh(runtime): Add static discovery method and support for JTAG programming for Ethernet devices
  • bug(tools): prevent ocpidoc error when port type not defined
  • bug(hdl base): sdp_pipeline replace use of fifo_1xn with fifo_2xn
  • bug(hdl base): fix fifo_2xn
  • bug(hdl base): fix incorrect combinatorial path when not arbitrating in sdp_node
  • bug(tools): fix ocpidoc build issue

Which issue(s) this MR closes

Closes #3286 (closed)

Merge request reports