Changed pciesvc driver compilation methods to support linux 6.1.123

[SahilChaudhari]

• changed hardcoded src/sonic-linux-kernel path to /lib/modules/<kernel_version>/ path
• changed platform.conf to use single kernel version variable instead changing all places

Why I did it

Work item tracking

• Microsoft ADO (number only):

How I did it

git clone https://github.com/sonic-net/sonic-buildimage.git
<path_to_sonic-builldimage>: make init
<path_to_sonic-builldimage>: make configure PLATFORM=pensando PLATFORM_ARCH=arm64
cd <path_to_sonic-builldimage>/platform/pensando/pensando-sonic-artifacts
<path_to_sonic-builldimage>/platform/pensando/pensando-sonic-artifacts: gh release download 1.87.0-SS-15-release
<path_to_sonic-builldimage>: NOJESSIE=1 NOSTRETCH=1 NOBUSTER=0 NOBULLSEYE=0 make target/sonic-pensando.tar

How to verify it

Load the SONiC image from ONIE and make sure the interfaces are UP. All containers are up. midplane ip should work.

Which release branch to backport (provide reason below if selected)

• 202205
• 202211
• 202305
• 202311
• 202405
• 202411
• 202505

Tested branch (Please provide the tested image version)

• master

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[prabhataravind]

@saiarcot895 @liushilongbuaa please help review

[liushilongbuaa]

@prabhataravind , why official build always succeed but PR build will fail randomly?

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[prabhataravind]

@qiluo-msft could you help merge? @prsunny for viz.

[kperumalbfn]

@prabhataravind Do we need this in 202411 and 202505?

[prabhataravind]

@prabhataravind Do we need this in 202411 and 202505?

We don't need in 202411, but I think we need in 202505. @SahilChaudhari I see #18536 and #21949 are in 202505, so I am assuming we need this in 202505. Please confirm and add request label for 202505.

[SahilChaudhari]

@prabhataravind Do we need this in 202411 and 202505?

We don't need in 202411, but I think we need in 202505. @SahilChaudhari I see #18536 and #21949 are in 202505, so I am assuming we need this in 202505. Please confirm and add request label for 202505.

@prabhataravind, I am not able to add label, there is no option for me to do so. Can you please add it for 202505? It is needed. Also is there permission needed to enable label for me?

@SahilChaudhari I have added the label. Looks like there is a conflict. Could you please raise a separate PR for 202505? @yejianquan for viz.