[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1e45558d-2a89-4cb7-a855-2682b54bbf12@moroto.mountain>
Date: Mon, 18 Mar 2024 10:46:42 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Ayush Tiwari <ayushtiw0110@...il.com>
Cc: Larry.Finger@...inger.net, florian.c.schilhabel@...glemail.com,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
linux-staging@...ts.linux.dev, outreachy@...ts.linux.dev
Subject: Re: [PATCH] staging: rtl8712: aggregate conditional statements
On Sun, Mar 17, 2024 at 11:36:17PM +0530, Ayush Tiwari wrote:
> Aggregate the two conditional statements into one conditional
> statement to reduce code length and simplify the code structure.
>
> Signed-off-by: Ayush Tiwari <ayushtiw0110@...il.com>
I'm not a fan of this sort of thing. The new code is fine but the
original code was fine. If you were going to be taking over the
maintainership of the rtl8712 driver, then you could do whatever you
want. But if you're just sending drive by patches, then it's just leave
the original code as is. You might be right. But it's not worth
debating or even thinking about for more than a second or two.
Someone was complaining about my code recently where I tend to break
things up into separate if statements and they were like "You could
combine them all on one line", and I'm like, "Yeah. It was that way to
begin with but I was fixing some issues and I deliberately separated it
out for readability." So that's one life hack which that if you don't
like someone's code style, just find some mistakes and re-write it.
regards,
dan carpenter
Powered by blists - more mailing lists