From fce584cde667f7bdef503de8b5a04438308537f9 Mon Sep 17 00:00:00 2001
From: Michael Rupp <95718139+mykrupp@users.noreply.github.com>
Date: Wed, 11 Jan 2023 13:37:30 -0500
Subject: [PATCH] fix bug where SEGGER_RTT_MAX_NUM_UP_BUFFERS doesn't get set
 by passing segger_rtt_max_num_down_buffers as a command line argument
 (#24350)

---
 third_party/jlink/segger_rtt/RTT/BUILD.gn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/third_party/jlink/segger_rtt/RTT/BUILD.gn b/third_party/jlink/segger_rtt/RTT/BUILD.gn
index 138e947baf3faa..defad76177f9f5 100644
--- a/third_party/jlink/segger_rtt/RTT/BUILD.gn
+++ b/third_party/jlink/segger_rtt/RTT/BUILD.gn
@@ -65,7 +65,7 @@ buildconfig_header("rtt_buildconfig") {
   }
   if (segger_rtt_max_num_down_buffers != -1) {
     defines +=
-        [ "SEGGER_RTT_MAX_NUM_UP_BUFFERS=${segger_rtt_max_num_down_buffers}" ]
+        [ "SEGGER_RTT_MAX_NUM_DOWN_BUFFERS=${segger_rtt_max_num_down_buffers}" ]
   }
   if (segger_rtt_mode_default != -1) {
     defines += [ "SEGGER_RTT_MODE_DEFAULT=${segger_rtt_mode_default}" ]