From: patchwork-bot+netdevbpf@kernel.org
To: Mike Rapoport <rppt@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, manishc@marvell.com, pabeni@redhat.com,
ecree.xilinx@gmail.com, przemyslaw.kitszel@intel.com,
skalluru@marvell.com, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-net-drivers@amd.com,
netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH 0/4] drivers/net/ethernet: replace __get_free_pages() with kmalloc()
Date: Wed, 08 Jul 2026 08:50:11 +0000 [thread overview]
Message-ID: <178350061164.2381125.12226069469974368415.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701-b4-drivers-ethernet-v1-0-58776615db6e@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 01 Jul 2026 16:57:17 +0300 you wrote:
> This is a (small) part of larger work of replacing page allocator calls
> with kmalloc.
>
> My initial intention a few month ago was to remove ugly casts [1], but then
> willy pointed out that Linus objected to something like this [2] and it
> looks like more than a decade old technical debt.
>
> [...]
Here is the summary with links:
- [1/4] bnx2x: use kzalloc() to allocate mac filtering list
https://git.kernel.org/netdev/net-next/c/28a236c54c9a
- [2/4] ice: use kzalloc() to allocate staging buffer for reading from GNSS
https://git.kernel.org/netdev/net-next/c/764f2a0c6d1e
- [3/4] sfc/siena: use kmalloc() to allocate logging buffer
https://git.kernel.org/netdev/net-next/c/50bfc5eac4cb
- [4/4] sfc: use kmalloc() to allocate logging buffer
https://git.kernel.org/netdev/net-next/c/e8cfc70720ea
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:[~2026-07-08 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 13:57 [Intel-wired-lan] [PATCH 0/4] drivers/net/ethernet: replace __get_free_pages() with kmalloc() Mike Rapoport (Microsoft)
2026-07-01 13:57 ` [Intel-wired-lan] [PATCH 1/4] bnx2x: use kzalloc() to allocate mac filtering list Mike Rapoport (Microsoft)
2026-07-02 13:52 ` Przemek Kitszel
2026-07-02 14:35 ` Mike Rapoport
2026-07-01 13:57 ` [Intel-wired-lan] [PATCH 2/4] ice: use kzalloc() to allocate staging buffer for reading from GNSS Mike Rapoport (Microsoft)
2026-07-02 13:49 ` Przemek Kitszel
2026-07-02 14:40 ` Mike Rapoport
2026-07-03 9:34 ` Przemek Kitszel
2026-07-07 13:33 ` Loktionov, Aleksandr
2026-07-01 13:57 ` [Intel-wired-lan] [PATCH 3/4] sfc/siena: use kmalloc() to allocate logging buffer Mike Rapoport (Microsoft)
2026-07-01 17:01 ` Edward Cree
2026-07-01 13:57 ` [Intel-wired-lan] [PATCH 4/4] sfc: " Mike Rapoport (Microsoft)
2026-07-01 16:59 ` Edward Cree
2026-07-08 8:50 ` 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=178350061164.2381125.12226069469974368415.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-net-drivers@amd.com \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=rppt@kernel.org \
--cc=skalluru@marvell.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