[kvalo-ath:master] BUILD SUCCESS 610b78b97bad8f3e77c27a15e9a03cbbb4109697

configs skipped: 15 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alphaallyesconfig gcc alphabuildonly-randconfig-r001-20230517 gcc alphabuildonly-randconfig-r002-20230517 gcc

[kvalo-ath:ath-next] BUILD SUCCESS df8e3729ffc0aa645839693f74ee7b6d999cdf64

configs tested: 258 configs skipped: 19 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alphaallyesconfig gcc alphabuildonly-randconfig-r001-20230517 gcc alpha

[kvalo-ath:ath-qca] BUILD SUCCESS 8b9ad0d421a366a57fa39204573a0e2bb63c8d88

configs skipped: 8 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alphaallyesconfig gcc alpha defconfig gcc alpharandconfig-r024-20230517 gcc alpha

[kvalo-ath:pending] BUILD SUCCESS 02c15ab2f967c68fe7de251df57e5a427a8f8b2e

configs tested: 262 configs skipped: 17 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alphaallyesconfig gcc alphabuildonly-randconfig-r001-20230517 gcc alphabuildonly-randconfig

[kvalo-ath:master-pending] BUILD SUCCESS 7038ad3258aa179ab0699ea437522e2290b5331a

tested: 215 configs skipped: 13 The following configs have been built successfully. More configs may be tested in the coming days. tested configs: alphaallyesconfig gcc alphabuildonly-randconfig-r001-20230517 gcc alphabuildonly-randconfig-r002

[PATCH v2 9/9] wifi: ath10k: Use RMW accessors for changing LNKCTL

Don't assume that only the driver would be accessing LNKCTL. ASPM policy changes can trigger write to LNKCTL outside of driver's control. Use RMW capability accessors which does proper locking to avoid losing concurrent updates to the register value. On restore, clear the ASPMC field properly.

Re: [PATCH v2 9/9] wifi: ath10k: Use RMW accessors for changing LNKCTL

Ilpo Järvinen writes: > Don't assume that only the driver would be accessing LNKCTL. ASPM > policy changes can trigger write to LNKCTL outside of driver's control. > > Use RMW capability accessors which does proper locking to avoid losing > concurrent updates to the register value. On restore,