[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aYMR1Q-Fifzts8gH@stanley.mountain>
Date: Wed, 4 Feb 2026 12:31:01 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: KrishnaAgarwal1308 <krishnaworkemail1308@...il.com>
Cc: Andy Shevchenko <andy@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
dri-devel@...ts.freedesktop.org, linux-fbdev@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Revert "staging: fbtft: remove goto from
define_fbtft_write_reg macro and clarify empty modifier fbtft-bus.c"
On Tue, Feb 03, 2026 at 10:17:27AM +0530, KrishnaAgarwal1308 wrote:
> Replace the goto-based error handling in the define_fbtft_write_reg macro with an
> early return while ensuring va_end() is called on all exit paths.
>
> Also add a short comment explaining the empty modifier argument used
> for native byte-order writes, instead of introducing an identity macro.
>
> No functional change intended.
>
> This reverts commit 6eec69e273e124dca8549fc52b0958b2953085ee. As per maintainer's feedback.
>
> Signed-off-by: Krishna Agarwal <krishnaworkemail1308@...il.com>
> ---
There is no need to revert the commit because we weren't going to apply
it.
Also checkpatch is going to complain about return statements the same
way it complains about gotos. Actually, I'm surprised checkpatch
complains about gotos. Does it differentiate between local gotos?
I can't be bothered to check. #LazyWeb
regards,
dan carpenter
Powered by blists - more mailing lists