User Tools

Site Tools


en:users:drivers:ath10k:codingstyle

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
en:users:drivers:ath10k:codingstyle [2018/08/24 09:30]
Kalle Valo [Naming] Add register/unregister examples
en:users:drivers:ath10k:codingstyle [2023/08/01 21:12]
Jeff Johnson [Error path]
Line 70: Line 70:
  
 <​code>​struct ath10k *ar = ptr; <​code>​struct ath10k *ar = ptr;
-struct ath10k_pci *ar_sdio ​= ath10k_pci_priv(ar);</​code>​+struct ath10k_pci *ar_pci ​= ath10k_pci_priv(ar);</​code>​
 For consistency always use the main context (struct ath10k *ar) as function parameter, don't use hif specific context. ​ For consistency always use the main context (struct ath10k *ar) as function parameter, don't use hif specific context. ​
  
Line 105: Line 105:
  
  
-<​code>​ath10k_warn("​failed to associate peer STA %pM\n: %d",+<​code>​ath10k_warn("​failed to associate peer STA %pM: %d\n",
             sta->​addr,​ ret);</​code>​             sta->​addr,​ ret);</​code>​
-Try to start the warning messages with the the verb "​failed"​ if possible. Warning and error messages start with lower case. +Try to start the warning messages with the verb "​failed"​ if possible. Warning and error messages start with lower case. 
  
 ath10k_warn() is used for errors where it might be possible to recover and ath10k_err() for errors when it's not possible to recover in any way.  ath10k_warn() is used for errors where it might be possible to recover and ath10k_err() for errors when it's not possible to recover in any way. 
  
-Dan Carpenters g+ post about error paths: [[https://plus.google.com/u/0/106378716002406849458/posts/dnanfhQ4mHQ|https://plus.google.com/u/0/106378716002406849458/posts/dnanfhQ4mHQ]] +Dan Carpenter'​s ​post about error paths: [[https://staticthinking.wordpress.com/2022/04/28/free-the-last-thing-style/|https://staticthinking.wordpress.com/2022/04/28/free-the-last-thing-style/]] 
  
  
Line 127: Line 127:
 <​code>​int ath10k_mac_start(struct ath10k *ar)</​code>​ <​code>​int ath10k_mac_start(struct ath10k *ar)</​code>​
  
-For each component use function names create/​destroy for allocating and freeing something, register/​unregister for initialising ​and cleaning up them afterwards and start/stop to temporarily pause something. ​+For each component use function names create/​destroy for allocating and freeing something, register/​unregister for initializing ​and cleaning up them afterwards and start/stop to temporarily pause something. ​
  
 Example: ​ Example: ​
Line 154: Line 154:
 ath10k_warn() should be used when ath10k still continues to work, for example then some limit has been reached or an unknown event has been received. It's also rate limited. ath10k_warn() should be used when ath10k still continues to work, for example then some limit has been reached or an unknown event has been received. It's also rate limited.
  
-ath10k_err() should be used when a fatal error has been detected and ath10k will shut itself down, for example during driver ​initialisation ​or firmware recover fails. It is NOT rate limited.+ath10k_err() should be used when a fatal error has been detected and ath10k will shut itself down, for example during driver ​initialization ​or firmware recover fails. It is NOT rate limited.
  
 Examples: Examples:
Line 165: Line 165:
 Use ath10k_dbg() or ath10k_dbg_dump(). Use ath10k_dbg() or ath10k_dbg_dump().
  
-The format string for ath10k_dbg() should start with debug level followed by name of the command or event and then parameters. All uppercase ​and no commas, colons or periods.+The format string for ath10k_dbg() should start with debug level followed by name of the command or event and then parameters. All lowercase ​and no commas, colons or periods.
  
 Examples: Examples:
en/users/drivers/ath10k/codingstyle.txt ยท Last modified: 2024/05/05 04:24 by Kalle Valo