lipengfei28 commented on PR #13520:
URL: https://github.com/apache/nuttx/pull/13520#issuecomment-2369998003

   commit 8288fe4e305bb905fa3ef18d24f895cf5ca33359 (HEAD -> master, 
apache/master)
   Author: chao an <[email protected]>
   Date:   Mon Sep 23 08:59:15 2024 +0800
   
       Revert "toolchain/ghs: Fix CONFIG_SCHED_CRITMONITOR_MAXTIME_XXX "zero 
used for undefined preprocessing identifier" warnings"
       
       move private define to public
       
       This reverts commit 236678d730220138416724d2cab25d6e1bd2ce9d.
       
       Signed-off-by: chao an <[email protected]>
   
   commit a5b85fcd961fb8a62fb31eb88a74f4c64406a2d7
   Author: wangjianyu3 <[email protected]>
   Date:   Mon Sep 23 18:44:17 2024 +0800
   
       misc/rpmsgdev: Fix invalid pointer error when there are more than one 
remotes
       
       Test: (see tests/testcases/rpmsgdev for details)
         # 1. Register dummy device
         testdev -d 0 -r "/dev/ttyGNSS0"
         # 2. Call rpmsgdev_export() to export the device to remote
         testdev -d 2 -c "droid" -l "/dev/ttyGNSS0"
       
       Log:
         [ap] arm_busfault: PANIC!!! Bus Fault:
         [ap] arm_busfault:        IRQ: 5 regs: 0x3c434e44
         [ap] arm_busfault:        BASEPRI: 00000000 PRIMASK: 00000000 IPSR: 
00000005 CONTROL: 00000004
         [ap] arm_busfault:        CFSR: 00008200 HFSR: 00000000 DFSR: 00000000 
BFAR: 00000000 AFSR: 00040000
         [ap] arm_busfault: Bus Fault Reason:
         [ap] arm_busfault:        Precise data bus error
         [ap] dump_assert_info: Current Version: NuttX ****** ***** *** 12.3.0 
********** Sep 23 2024 18:35:50 arm
         [ap] dump_assert_info: Assertion failed panic: at file: 
armv8-m/arm_busfault.c:113 task: testdev process: testdev 0x2c86ca75
       
   This commit build is ok


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to