From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Greg Sword <gregsword0@gmail.com>,
Zhu Yanjun <yanjun.zhu@linux.dev>,
zyjzyj2000@gmail.com, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>
Subject: Re: [PATCH v3 1/1] RDMA/rxe: Avoid -Wflex-array-member-not-at-end warnings
Date: Wed, 24 Dec 2025 17:32:27 +0900 [thread overview]
Message-ID: <62e3bf9f-3dd2-4fc9-b661-cacc93e84de9@embeddedor.com> (raw)
In-Reply-To: <20251224065107.GD11869@unreal>
> So please remember that both of you want the same thing, and let's keep the
> discussion focused on the technical issues.
Absolutely, we all care about the same and, to me, this[1] really marked
the end of this thread. So, thanks for your intervention, and thanks
Zhu for addressing that issue.
On my side, I'm off the rest of the year. Enjoy some time away from the
keyboard everyone, and happy holidays to those who have the chance.
-Gustavo
[1] https://lore.kernel.org/linux-rdma/20251223142055.GC11869@unreal/
prev parent reply other threads:[~2025-12-24 8:33 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
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 [this message]
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=62e3bf9f-3dd2-4fc9-b661-cacc93e84de9@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gregsword0@gmail.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