[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vc8tWKUpKS8yY52CdJ=mU-iqcrUCz32ZSSJixLA1bM0tQ@mail.gmail.com>
Date: Fri, 3 Aug 2018 12:10:31 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Finn Thain <fthain@...egraphics.com.au>,
Julia Lawall <julia.lawall@...6.fr>
Cc: zhong jiang <zhongjiang@...wei.com>,
Michael Schmitz <schmitzmic@...il.com>,
"James E . J . Bottomley" <jejb@...ux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
John Garry <john.garry@...wei.com>,
linux-scsi <linux-scsi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] scsi:NCR5380: remove same check condition in NCR5380_select
On Fri, Aug 3, 2018 at 5:24 AM, Finn Thain <fthain@...egraphics.com.au> wrote:
> On Thu, 2 Aug 2018, zhong jiang wrote:
>
>> The same check condition is redundant, so remove one of them.
>>
>
> If you are trying to find redundant code, your coccinelle script is
> dangerously flawed.
These days too many coccinelle helpers make people think they are
doing right "clean ups" when in the practice they bring the
regressions.
Julia, is possible by coccinelle to distinguish memory accesses versus
I/O? At least it would increase robustness in some cases.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists