From: patchwork-bot+netdevbpf@kernel.org
To: Julia Lawall <julia.lawall@inria.fr>
Cc: linux-hyperv@vger.kernel.org, kernel-janitors@vger.kernel.org,
keescook@chromium.org, christophe.jaillet@wanadoo.fr,
kuba@kernel.org, kasan-dev@googlegroups.com,
andreyknvl@gmail.com, dvyukov@google.com, iommu@lists.linux.dev,
linux-tegra@vger.kernel.org, robin.murphy@arm.com,
vdumpa@nvidia.com, virtualization@lists.linux-foundation.org,
xuanzhuo@linux.alibaba.com, linux-scsi@vger.kernel.org,
linaro-mm-sig@lists.linaro.org, linux-media@vger.kernel.org,
jstultz@google.com, Brian.Starkey@arm.com, labbott@redhat.com,
lmark@codeaurora.org, benjamin.gaignard@collabora.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, shailend@google.com,
linux-rdma@vger.kernel.org, mhi@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-btrfs@vger.kernel.org,
intel-gvt-dev@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, dave.hansen@linux.intel.com,
hpa@zytor.com, linux-sgx@vger.kernel.org
Subject: Re: [PATCH v2 00/24] use vmalloc_array and vcalloc
Date: Tue, 27 Jun 2023 16:40:23 +0000 [thread overview]
Message-ID: <168788402349.21860.17350888958370358926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230627144339.144478-1-Julia.Lawall@inria.fr>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jun 2023 16:43:15 +0200 you wrote:
> The functions vmalloc_array and vcalloc were introduced in
>
> commit a8749a35c399 ("mm: vmalloc: introduce array allocation functions")
>
> but are not used much yet. This series introduces uses of
> these functions, to protect against multiplication overflows.
>
> [...]
Here is the summary with links:
- [v2,02/24] octeon_ep: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/32d462a5c3e5
- [v2,04/24] gve: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/a13de901e8d5
- [v2,09/24] pds_core: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/906a76cc7645
- [v2,11/24] ionic: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/f712c8297e0a
- [v2,18/24] net: enetc: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/fa87c54693ae
- [v2,22/24] net: mana: use vmalloc_array and vcalloc
https://git.kernel.org/netdev/net-next/c/e9c74f8b8a31
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-06-27 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 14:43 [PATCH v2 00/24] use vmalloc_array and vcalloc Julia Lawall
2023-06-27 14:43 ` [PATCH v2 13/24] iommu/tegra: gart: " Julia Lawall
2023-06-27 16:40 ` patchwork-bot+netdevbpf [this message]
2023-07-06 1:35 ` [PATCH v2 00/24] " Martin K. Petersen
2023-07-11 16:31 ` (subset) " 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=168788402349.21860.17350888958370358926.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Brian.Starkey@arm.com \
--cc=andreyknvl@gmail.com \
--cc=benjamin.gaignard@collabora.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dave.hansen@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jstultz@google.com \
--cc=julia.lawall@inria.fr \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=shailend@google.com \
--cc=vdumpa@nvidia.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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).