[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05eed3d8321d0f355bf3dc59ffea3d6ab08135fa.camel@linux.ibm.com>
Date: Tue, 07 Feb 2023 22:25:09 +0300
From: James Bottomley <jejb@...ux.ibm.com>
To: Deepak R Varma <drv@...lo.com>
Cc: Khalid Aziz <khalid@...ehiking.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Saurabh Singh Sengar <ssengar@...rosoft.com>,
Praveen Kumar <kumarpraveen@...ux.microsoft.com>
Subject: Re: [PATCH] scsi: FlashPoint: Replace arithmetic addition by
bitwise OR
On Tue, 2023-02-07 at 23:16 +0530, Deepak R Varma wrote:
[...]
> James, there are a few other patch submissions for the scsi subsystem
> that I submitted in last few weeks. I sent couple of reminder request
> for comments on those submission, but still waiting. Could you please
> also review those and share your feedback?
The problem is basically that they don't fix a bug or introduce an
enhancement. Review bandwidth in SCSI is the main limiting factor for
any new patch, so we tend to concentrate on these two types. The main
problem with code replacement patches is that they do tend to introduce
inadvertent bugs in old drivers, which is why people are afraid to
review them. You can reduce the overhead of review by demonstrating
that the binary produced is unchanged (obviously this works for some
but not all of your patches), so a maintainer need only decide if they
like the change rather than worrying about it introducing a regression.
Regards,
James
Powered by blists - more mailing lists