From 0986ade905f40c17fb08c07533d4d2de176411b8 Mon Sep 17 00:00:00 2001
From: Peter Barker <pbarker@barker.dropbear.id.au>
Date: Thu, 8 Jul 2021 16:10:28 +1000
Subject: [PATCH] Blimp: remove misleading NOINLINE comment

NOINLINE hasn't been used in years in these files
---
 Blimp/GCS_Mavlink.cpp | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/Blimp/GCS_Mavlink.cpp b/Blimp/GCS_Mavlink.cpp
index 0ae2abef19..b0861d93e9 100644
--- a/Blimp/GCS_Mavlink.cpp
+++ b/Blimp/GCS_Mavlink.cpp
@@ -2,16 +2,6 @@
 
 #include "GCS_Mavlink.h"
 
-/*
- *  !!NOTE!!
- *
- *  the use of NOINLINE separate functions for each message type avoids
- *  a compiler bug in gcc that would cause it to use far more stack
- *  space than is needed. Without the NOINLINE we use the sum of the
- *  stack needed for each message type. Please be careful to follow the
- *  pattern below when adding any new messages
- */
-
 MAV_TYPE GCS_Blimp::frame_type() const
 {
     return blimp.get_frame_mav_type();