From: patchwork-bot+netdevbpf@kernel.org
To: Qianfeng Rong <rongqianfeng@vivo.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, sdf@fomichev.me,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, oss-drivers@corigine.com,
bpf@vger.kernel.org
Subject: Re: [PATCH v3 0/3] net: use vmalloc_array() to simplify code
Date: Tue, 19 Aug 2025 01:00:20 +0000 [thread overview]
Message-ID: <175556522029.2966773.8890220490164839233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250816090659.117699-1-rongqianfeng@vivo.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 16 Aug 2025 17:06:51 +0800 you wrote:
> Remove array_size() calls and replace vmalloc() with vmalloc_array() to
> simplify the code and maintain consistency with existing kmalloc_array()
> usage.
>
> vmalloc_array() is also optimized better, resulting in less instructions
> being used [1].
>
> [...]
Here is the summary with links:
- [v3,1/3] eth: intel: use vmalloc_array() to simplify code
https://git.kernel.org/netdev/net-next/c/4490d075c2d9
- [v3,2/3] nfp: flower: use vmalloc_array() to simplify code
https://git.kernel.org/netdev/net-next/c/fce214586f99
- [v3,3/3] ppp: use vmalloc_array() to simplify code
https://git.kernel.org/netdev/net-next/c/dad3280591ab
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:[~2025-08-19 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 9:06 Qianfeng Rong
2025-08-16 9:06 ` [PATCH v3 1/3] eth: intel: " Qianfeng Rong
2025-08-16 9:06 ` [PATCH v3 2/3] nfp: flower: " Qianfeng Rong
2025-08-16 9:06 ` [PATCH v3 3/3] ppp: " Qianfeng Rong
2025-08-19 1:00 ` 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=175556522029.2966773.8890220490164839233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rongqianfeng@vivo.com \
--cc=sdf@fomichev.me \
/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
all inboxes | Powered by JetHome®