Skip to content

Updated AITER/QoLA - #683

Open
Micky774 wants to merge 2 commits into
devfrom
zain/qola/aiter-update
Open

Updated AITER/QoLA#683
Micky774 wants to merge 2 commits into
devfrom
zain/qola/aiter-update

Conversation

@Micky774

@Micky774 Micky774 commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Description

Updates AITER/QoLA partner to ROCm/QoLA#8

Fixes # (issue)

Type of change

  • Documentation change (change only to the documentation, either a fix or a new content)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Infra/Build change
  • Code refactoring

Changes

Please list the changes introduced in this PR:

  • Change A
  • Change B

Checklist:

  • I have read and followed the contributing guidelines
  • The functionality is complete
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@Micky774 Micky774 added the ci-level 3 CI test level 3 label Jul 28, 2026
@ipanfilo

Copy link
Copy Markdown
Collaborator

What is motivation? Just switch to newer AITER or some specific functionality?

@Micky774

Micky774 commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

What is motivation? Just switch to newer AITER or some specific functionality?

Keeping w/ newer AITER to make it easier to maintain the a4w4 integration, since that'll need to be merged into AITER main.

Edit: I believe there were also some AITER/CK changes we needed to pick up (cc: @wangye805 )

@ipanfilo ipanfilo left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets make sure CI failures are irrelevant before merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-level 3 CI test level 3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants