From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: netdev@vger.kernel.org, leonro@nvidia.com, sthemmin@microsoft.com
Subject: Re: [PATCH iproute2-next 0/2] RDMA clang warning fixes
Date: Tue, 11 Jan 2022 16:30:13 +0000 [thread overview]
Message-ID: <164191861380.12736.2034538744802044982.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1641753491.git.leonro@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sun, 9 Jan 2022 20:41:37 +0200 you wrote:
> 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
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] rdma: Limit copy data by the destination size
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=b87671681e8a
- [iproute2-next,2/2] rdma: Don't allocate sparse array
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=bb4cc9cca408
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-11 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 18:41 [PATCH iproute2-next 0/2] RDMA clang warning fixes Leon Romanovsky
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 ` patchwork-bot+netdevbpf [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=164191861380.12736.2034538744802044982.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.