[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.23.453.2008280859300.10@nippy.intranet>
Date: Fri, 28 Aug 2020 09:21:22 +1000 (AEST)
From: Finn Thain <fthain@...egraphics.com.au>
To: Joe Perches <joe@...ches.com>
cc: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Denis Efremov <efremov@...ux.com>,
"David S. Miller" <davem@...emloft.net>,
Song Liu <song@...nel.org>, Al Viro <viro@...iv.linux.org.uk>,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ide@...r.kernel.org, linux-raid@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-m68k@...ts.linux-m68k.org
Subject: Re: [PATCH 17/19] z2ram: reindent
> @@ -109,34 +111,28 @@ static void get_z2ram(void)
...
> }
> -
> - return;
> }
>
It would be good to have a semantic patch for that change.
>
> - if (z2ram_map[z2ram_size] == 0) {
> + if (z2ram_map[z2ram_size] == 0)
> break;
> - }
>
And that one.
Reason being, a semantic patch only has to be debugged once, whereas
manual churn has to be done correctly over and over again.
TBH, this kind of transformation can happen when code is displayed.
It doesn't have to involve git at all. Otherwise, why have 5 billion
transistors? You'd be better off with an Amiga.
Powered by blists - more mailing lists