On Mon, Oct 26, 2026 at 2:54 PM himanshu bakshi <[email protected]> wrote: > > From: Himanshu Bakshi <[email protected]> > > The fbtft_init_dbg() macro is not being used, so delete it. > > Reviewed-by: Dan Carpenter [email protected] > > Signed-off-by: Himanshu Bakshi <[email protected]> > --- > drivers/staging/fbtft/fbtft.h | 7 ------- > 1 file changed, 7 deletions(-) > > diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h > index 40a7567df1eb..16459e4e0ba0 100644 > --- a/drivers/staging/fbtft/fbtft.h > +++ b/drivers/staging/fbtft/fbtft.h > @@ -420,13 +420,6 @@ module_spi_driver(fbtft_driver_spi_driver); > #define DEBUG_REQUEST_GPIOS_MATCH BIT(30) > #define DEBUG_VERIFY_GPIOS BIT(31) > > -#define fbtft_init_dbg(dev, format, arg...) \ > -do { \ > - if (unlikely((dev)->platform_data && \ > - (((struct fbtft_platform_data > *)(dev)->platform_data)->display.debug & DEBUG_DRIVER_INIT_FUNCTIONS))) \ > - dev_info(dev, format, ##arg); \ > -} while (0) > - > #define fbtft_par_dbg(level, par, format, arg...) \ > do { \ > if (unlikely((par)->debug & (level))) \ > -- > 2.56.0 >
Hi Andy, For testing, I have compiled the driver successfully and verified that fbtft_init_dbg() has no call sites in the kernel tree. Thank you for the review. Thanks and Regards, Himanshu Bakshi
