[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yq1ldldb1f7.fsf@ca-mkp.ca.oracle.com>
Date: Tue, 14 Oct 2025 17:55:18 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: "Gustavo A. R. Silva" <gustavo@...eddedor.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
"Gustavo A. R.
Silva" <gustavoars@...nel.org>,
Kashyap Desai
<kashyap.desai@...adcom.com>,
Sumit Saxena <sumit.saxena@...adcom.com>,
Shivasharan S <shivasharan.srikanteshwara@...adcom.com>,
Chandrakanth
patil <chandrakanth.patil@...adcom.com>,
"Martin K. Petersen"
<martin.petersen@...cle.com>,
megaraidlinux.pdl@...adcom.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH v2][next] scsi: megaraid_sas: Avoid a couple
-Wflex-array-member-not-at-end warnings
Gustavo,
>> I'll leave it up to Martin, but I think going forwards it would be
>> helpful if you could indicate that you've checked that the binary
>> layout before and after is unchanged and thus the risk of merging the
>> patch is low.
>
> Absolutely. I'll do that.
For patches like these it really helps. I only have the ability to
validate changes against a very small subset of the SCSI drivers we
support in the kernel.
--
Martin K. Petersen
Powered by blists - more mailing lists