From ae420f6bb47e2cade2115b5e4bf53467ca2ad555 Mon Sep 17 00:00:00 2001 From: AnnsAnn Date: Thu, 18 Sep 2025 14:01:53 +0200 Subject: [PATCH] doc/guides/misc/dev_best_practices: remove outdated MSP430 info Co-authored-by: Marian Buschsieweke --- doc/guides/misc/dev_best_practices.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/guides/misc/dev_best_practices.md b/doc/guides/misc/dev_best_practices.md index 405dd418f4..29ef151650 100644 --- a/doc/guides/misc/dev_best_practices.md +++ b/doc/guides/misc/dev_best_practices.md @@ -145,7 +145,5 @@ If you want to analyze the static memory consumption of your code you can use * Code can request the amount of memory it needs on runtime * On most platforms: the size of the heap is `sizeof()-sizeof()` * If you reduce your usage of static memory your heap gets bigger -* On some platforms calling `free()` will not or not always make heap memory available again - (see [Oneway Malloc on MSP430](https://doc.riot-os.org/group__oneway__malloc.html)) * Programmer needs to handle failed memory allocation calls at runtime * Static code analysis is unable to find errors regarding memory management