[action] [PR:3968] [Marvell-Teralynx][PFCWD]: Fix pfc_detect filename to align with asic_type#4322
Open
mssonicbld wants to merge 1 commit intosonic-net:202511from
Open
[action] [PR:3968] [Marvell-Teralynx][PFCWD]: Fix pfc_detect filename to align with asic_type#4322mssonicbld wants to merge 1 commit intosonic-net:202511from
mssonicbld wants to merge 1 commit intosonic-net:202511from
Conversation
…_type **Description:** Change pfc_detect filename from pfc_detect_marvell_teralynx.lua to pfc_detect_marvell-teralynx.lua to align with asic_type naming convention. This fix addresses the naming inconsistency introduced in PR sonic-net#3252 and ensures the filename matches the expected asic_type format used throughout the codebase. **What I did:** - Renamed pfc_detect_marvell_teralynx.lua to pfc_detect_marvell-teralynx.lua - Updated Makefile.am to reference the renamed file **Why I did it:** - Fix the naming of pfc_detect file to align with asic_type convention - Maintain consistency with platform naming standards **How I verified it:** Run the pfc_wd SONiC PTF test cases. **Which release branch to backport (provide reason below if selected):** - [ ] 202405 - [ ] 202411 - [x] 202505 - [x] 202511 **Tested branch (Please provide the tested image version):** 202505 <!-- Please make sure you have read and understood the contribution guildlines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md 1. Make sure your commit includes a signature generted with `git commit -s` 2. Make sure your commit title follows the correct format: [component]: description 3. Make sure your commit message contains enough details about the change and related tests 4. Make sure your pull request adds related reviewers, asignees, labels Please also provide the following information in this pull request: --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
Collaborator
Author
|
Original PR: #3968 |
4 tasks
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-swss |
Collaborator
Author
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
vmittal-msft
approved these changes
Mar 27, 2026
|
/azpw run |
Collaborator
Author
|
Retrying failed(or canceled) jobs... |
Collaborator
Author
|
Build not found. Please close and reopen the PR or rebase your branch to trigger a new build. |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
3 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.
Description:
Change pfc_detect filename from pfc_detect_marvell_teralynx.lua to pfc_detect_marvell-teralynx.lua to align with asic_type naming convention.
This fix addresses the naming inconsistency introduced in PR #3252 and ensures the filename matches the expected asic_type format used throughout the codebase.
What I did:
Why I did it:
How I verified it:
Run the pfc_wd SONiC PTF test cases.
Which release branch to backport (provide reason below if selected):
Tested branch (Please provide the tested image version):
202505
Signed-off-by: Sonic Build Admin sonicbld@microsoft.com