lorawan/nvm: do not call settings_save() after writing individual settings

aurel32 · fabiobaltieri · commit ea995f6378f7 · 2024-05-01T22:56:34.000+01:00
The lorawan subsystem do not use settings handler, and instead uses
individual calls to settings_save_one(). With this strategy there is no
need to call settings_save() at the end.

Signed-off-by: Aurelien Jarno &lt;aurelien@aurel32.net&gt;
diff --git a/subsys/lorawan/nvm/lorawan_nvm_settings.c b/subsys/lorawan/nvm/lorawan_nvm_settings.c
@@ -77,8 +77,6 @@ static void lorawan_nvm_save_settings(uint16_t nvm_notify_flag)
 			}
 		}
 	}
-
-	settings_save();
 }
 
 void lorawan_nvm_data_mgmt_event(uint16_t flags)

Original file line number	Diff line number	Diff line change
`@@ -77,8 +77,6 @@ static void lorawan_nvm_save_settings(uint16_t nvm_notify_flag)`
`77`	`77`	`}`
`78`	`78`	`}`
`79`	`79`	`}`
`80`		`-`
`81`		`- settings_save();`
`82`	`80`	`}`
`83`	`81`
`84`	`82`	`void lorawan_nvm_data_mgmt_event(uint16_t flags)`