From 9d7024f89eaf8dcc522da4b5f77c35cb42b660bb Mon Sep 17 00:00:00 2001
From: Thomas Watson <twatson52@icloud.com>
Date: Mon, 30 Dec 2024 11:57:51 -0600
Subject: [PATCH] AP_HAL_ChibiOS: Storage: fix up delay comment

EXPECT_DELAY_MS was used in direct contravention of the comment so it
must be okay. Even when it wasn't and the comment was accurate,
expecting a delay off the main thread never worked properly anyway.
---
 libraries/AP_HAL_ChibiOS/Storage.cpp | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/libraries/AP_HAL_ChibiOS/Storage.cpp b/libraries/AP_HAL_ChibiOS/Storage.cpp
index 7f8fc2819b..dc0ce2f074 100644
--- a/libraries/AP_HAL_ChibiOS/Storage.cpp
+++ b/libraries/AP_HAL_ChibiOS/Storage.cpp
@@ -421,12 +421,7 @@ bool Storage::_flash_erase_sector(uint8_t sector)
     // erasing a page can take long enough that USB may not initialise properly if it happens
     // while the host is connecting. Only do a flash erase if we have been up for more than 4s
     for (uint8_t i=0; i<STORAGE_FLASH_RETRIES; i++) {
-        /*
-          a sector erase stops the whole MCU. We need to setup a long
-          expected delay, and not only when running in the main
-          thread.  We can't use EXPECT_DELAY_MS() as it checks we are
-          in the main thread
-         */
+        // a sector erase stops the whole MCU so set up a long expected delay
         EXPECT_DELAY_MS(1000);
 #if AP_FLASH_STORAGE_DOUBLE_PAGE
         if (hal.flash->erasepage(_flash_page+sector) && hal.flash->erasepage(_flash_page+sector+1)) {