This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
en:users:drivers:ath10k:submittingpatches [2020/06/09 12:52] Kalle Valo Write about hardware families and Tested-on tags |
en:users:drivers:ath10k:submittingpatches [2020/06/09 12:56] Kalle Valo [Tested-on tag] Use examples with code tags |
||
---|---|---|---|
Line 78: | Line 78: | ||
Few examples: | Few examples: | ||
+ | <code> | ||
Tested-on: WCN3990 hw1.0 WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1 | Tested-on: WCN3990 hw1.0 WLAN.HL.3.1-01040-QCAHLSWMTPLZ-1 | ||
Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00029 | Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00029 | ||
Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00110-QCARMSWP-1 | Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00110-QCARMSWP-1 | ||
Tested-on: QCA9888 hw2.0 10.4-3.10-00047 | Tested-on: QCA9888 hw2.0 10.4-3.10-00047 | ||
+ | </code> | ||
Tested-on tag should be in every patch, as non-trivial patches should not be submitted without testing. For trivial patches it's ok to skip Tested-on tag but then it should say "Compile tested only". | Tested-on tag should be in every patch, as non-trivial patches should not be submitted without testing. For trivial patches it's ok to skip Tested-on tag but then it should say "Compile tested only". |