On Mon, 26 Jan 2026 16:45:18 +0000 Bruce Richardson <[email protected]> wrote:
> The error message about the interrupt being unallocated is called from > multiple positions, so if seen in the logs the user cannot tell which > function is actually generating the message. Add function name and line > number info to the message to clarify things. > > Signed-off-by: Bruce Richardson <[email protected]> > --- > lib/eal/common/eal_common_interrupts.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/lib/eal/common/eal_common_interrupts.c > b/lib/eal/common/eal_common_interrupts.c > index b42fa862f3..a2a310750a 100644 > --- a/lib/eal/common/eal_common_interrupts.c > +++ b/lib/eal/common/eal_common_interrupts.c > @@ -17,7 +17,7 @@ > /* Macros to check for valid interrupt handle */ > #define CHECK_VALID_INTR_HANDLE(intr_handle) do { \ > if (intr_handle == NULL) { \ > - EAL_LOG(DEBUG, "Interrupt instance unallocated"); \ > + EAL_LOG(DEBUG, "%s, ln %d: Interrupt instance unallocated", > __func__, __LINE__); \ Using "ln %d" seems different from other places. Maybe EAL_LOG(DEBUG, "%s:%d Interrupt instance unallocated", __FILE__, __LINE__); \
