From: Leon Romanovsky <leon@kernel.org>
To: netdev@vger.kernel.org
Cc: Leon Romanovsky <leonro@nvidia.com>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH iproute2-next 0/2] RDMA clang warning fixes
Date: Sun, 9 Jan 2022 20:41:37 +0200 [thread overview]
Message-ID: <cover.1641753491.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
This is followup to Stephen's series [1].
Thanks
[1] https://lore.kernel.org/all/20220108204650.36185-1-sthemmin@microsoft.com
Leon Romanovsky (2):
rdma: Limit copy data by the destination size
rdma: Don't allocate sparse array
rdma/res-srq.c | 14 +++++---------
rdma/res.c | 6 +++---
2 files changed, 8 insertions(+), 12 deletions(-)
--
2.33.1
next reply other threads:[~2022-01-09 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 18:41 Leon Romanovsky [this message]
2022-01-09 18:41 ` [PATCH iproute2-next 1/2] rdma: Limit copy data by the destination size Leon Romanovsky
2022-01-09 18:41 ` [PATCH iproute2-next 2/2] rdma: Don't allocate sparse array Leon Romanovsky
2022-01-11 16:30 ` [PATCH iproute2-next 0/2] RDMA clang warning fixes patchwork-bot+netdevbpf
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=cover.1641753491.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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;
as well as URLs for NNTP newsgroup(s).