From 6e9b1b344b7f7b04a2ae4ace0a1d191f63d03396 Mon Sep 17 00:00:00 2001 From: Aidan MacDonald Date: Wed, 30 Mar 2022 18:23:59 +0100 Subject: buflib: remove buflib_print_allocs / buflib_print_blocks These don't have any users and there is already another way to print blocks (which is actually used by the debug menu). Change-Id: Ic6a4f874c6499c42bc046e8af3e4aaddc9e68276 --- firmware/include/core_alloc.h | 4 ---- 1 file changed, 4 deletions(-) (limited to 'firmware/include/core_alloc.h') diff --git a/firmware/include/core_alloc.h b/firmware/include/core_alloc.h index 67fe99dfdc..f535fc1f6e 100644 --- a/firmware/include/core_alloc.h +++ b/firmware/include/core_alloc.h @@ -25,10 +25,6 @@ void core_check_valid(void); /* DO NOT ADD wrappers for buflib_buffer_out/in. They do not call * the move callbacks and are therefore unsafe in the core */ -#ifdef BUFLIB_DEBUG_BLOCKS -void core_print_allocs(void (*print)(const char*)); -void core_print_blocks(void (*print)(const char*)); -#endif #ifdef BUFLIB_DEBUG_BLOCK_SINGLE int core_get_num_blocks(void); void core_print_block_at(int block_num, char* buf, size_t bufsize); -- cgit v1.2.3