From ffe4493982f2f47098f36682e4e6ca964048b903 Mon Sep 17 00:00:00 2001
From: WillianChan <chentingwei@rt-thread.com>
Date: Fri, 5 Mar 2021 16:15:51 +0800
Subject: [PATCH] [kernel][Konfig]modify Kconfig file

Signed-off-by: WillianChan <chentingwei@rt-thread.com>
---
 src/Kconfig | 26 ++++++++++++--------------
 1 file changed, 12 insertions(+), 14 deletions(-)

diff --git a/src/Kconfig b/src/Kconfig
index 803c827e51..aa8e514e5c 100644
--- a/src/Kconfig
+++ b/src/Kconfig
@@ -284,21 +284,19 @@ menu "Memory Management"
 
     endchoice
 
-    if RT_USING_SMALL_MEM
-        config RT_USING_MEMTRACE
-            bool "Enable memory trace"
-            default n
-            help
-                When enable RT_USING_MEMTRACE with shell, developer can call cmd:
-                1. memtrace
-                   to dump memory block information.
-                2. memcheck
-                   to check memory block to avoid memory overwritten.
+    config RT_USING_MEMTRACE
+        bool "Enable memory trace"
+        default n
+        help
+            When enable RT_USING_MEMTRACE with shell, developer can call cmd:
+            1. memtrace
+                to dump memory block information.
+            2. memcheck
+                to check memory block to avoid memory overwritten.
 
-                And developer also can call memcheck() in each of scheduling
-                to check memory block to find which thread has wrongly modified
-                memory.
-    endif
+            And developer also can call memcheck() in each of scheduling
+            to check memory block to find which thread has wrongly modified
+            memory.
 
     config RT_USING_HEAP
         bool