From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sumit Saxena <sumit.saxena@broadcom.com>,
Shivasharan S <shivasharan.srikanteshwara@broadcom.com>,
Chandrakanth patil <chandrakanth.patil@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v2][next] scsi: megaraid_sas: Avoid a couple -Wflex-array-member-not-at-end warnings
Date: Tue, 14 Oct 2025 17:55:18 -0400 [thread overview]
Message-ID: <yq1ldldb1f7.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <a157b190-74f4-443b-b52f-1fe0280f9bb3@embeddedor.com> (Gustavo A. R. Silva's message of "Wed, 8 Oct 2025 10:28:38 +0100")
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
next prev parent reply other threads:[~2025-10-14 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 11:56 [PATCH v2][next] scsi: megaraid_sas: Avoid a couple -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-10-07 10:43 ` Gustavo A. R. Silva
2025-10-07 11:59 ` James Bottomley
2025-10-07 14:18 ` Gustavo A. R. Silva
2025-10-07 22:56 ` James Bottomley
2025-10-08 9:28 ` Gustavo A. R. Silva
2025-10-14 21:55 ` Martin K. Petersen [this message]
2025-10-14 21:47 ` Martin K. Petersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1ldldb1f7.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=kashyap.desai@broadcom.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox