From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>,
zyjzyj2000@gmail.com, jgg@ziepe.ca, leon@kernel.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: Re: [PATCH v3 1/1] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings
Date: Tue, 23 Dec 2025 14:54:36 +0900 [thread overview]
Message-ID: <256da54b-519f-461d-9586-10b26ef7568e@embeddedor.com> (raw)
In-Reply-To: <24901de5-f7dc-4070-8745-df114ce1ff75@linux.dev>
On 12/23/25 14:44, Zhu Yanjun wrote:
>
> 在 2025/12/22 21:34, Gustavo A. R. Silva 写道:
>>
>>>>>>> V2->V3: Replace struct ib_sge with struct rxe_sge
>>>>>>
>>>>>> What are you doing?
>>>>>
>>>>> Because struct rxe_sge differs from struct ib_sge, I aligned it to use the same structure.
>>>>
>>>> Listen, this is not how things are done upstream. Read what I previously commented:
>>>>
>>>>>> You're making a mess of this whole thing. Please, don't make changes
>>>>>> to my patches on your own.
>>>>
>>>> and please, learn how to properly submit patch series.
>>>>
>>>> Lastly, do the changes that you want/need to implement in your code, and don't
>>>> submit my patch as part of those changes again.
>>>
>>> You can correct this patch by yourself.
>>
>> https://lore.kernel.org/linux-hardening/ad8987ae-b7fe-47af-a1d2-5055749011c0@embeddedor.com/
>
> You need to do some changes in your commit.
This is what you haven't understood yet. If the original code is wrong (e.g. is
currently using struct ib_sge instead of struct rxe_sge or the other way around),
then _that_ code should be fixed _first_, regardless of any other patch that might
be applied on top of it.
-Gustavo
next prev parent reply other threads:[~2025-12-23 5:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 4:41 [PATCH v3 1/1] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings Zhu Yanjun
2025-12-23 5:03 ` Gustavo A. R. Silva
2025-12-23 5:10 ` Zhu Yanjun
2025-12-23 5:18 ` Gustavo A. R. Silva
2025-12-23 5:26 ` Zhu Yanjun
2025-12-23 5:34 ` Gustavo A. R. Silva
2025-12-23 5:44 ` Zhu Yanjun
2025-12-23 5:54 ` Gustavo A. R. Silva [this message]
2025-12-23 6:46 ` Zhu Yanjun
2025-12-23 9:28 ` Gustavo A. R. Silva
2025-12-23 16:02 ` Zhu Yanjun
2025-12-23 14:20 ` Leon Romanovsky
2025-12-23 16:13 ` Zhu Yanjun
2025-12-23 9:34 ` Gustavo A. R. Silva
2025-12-23 16:38 ` Greg Sword
2025-12-23 16:59 ` Gustavo A. R. Silva
2025-12-23 17:19 ` Greg Sword
2025-12-23 17:26 ` Gustavo A. R. Silva
2025-12-24 6:51 ` Leon Romanovsky
2025-12-24 8:32 ` Gustavo A. R. Silva
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=256da54b-519f-461d-9586-10b26ef7568e@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--cc=zyjzyj2000@gmail.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