On Sun, Jan 05, 2025 at 12:49:37PM -0500, Sandeep Salwan wrote: > This patch removes unnecessary parentheses around the conditional checks (!txbuflen) and (bpp > 8) in fbtft-core.c. According to the kernel coding style, reducing superfluous parentheses makes the code more readable and straightforward. There are no functional changes; it’s purely a cleanup to align the code with kernel style guidelines. Please wrap your changelog at 72 columns like your editor asked you to. > > Signed-off-by: Sandeep Salwan <salwansandeep5@xxxxxxxxx> > --- > drivers/staging/fbtft/fbtft-core.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c > index 4cfa494243b9..b4e9d6000b9a 100644 > --- a/drivers/staging/fbtft/fbtft-core.c > +++ b/drivers/staging/fbtft/fbtft-core.c > @@ -664,7 +664,7 @@ struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, > txbuflen = 0; > > #ifdef __LITTLE_ENDIAN > - if ((!txbuflen) && (bpp > 8)) > + if (!txbuflen && bpp > 8) No, please see the zillions of times I have rejected changes like this in the past on the mailing list. checkpatch.pl is wrong here. We write code for people first, compilers second. With your change, now you need to look up the order of operations (quick, which is comes first in order, '&&' or '!' or '>')? With the () there, you know what the intent is, and what the order is, without having to always know what comes before what. thanks, greg k-h
