From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, fw@strlen.de, horms@kernel.org
Subject: Re: [PATCH net-next 1/7] netfilter: xt_hashlimit: replace vmalloc calls with kvmalloc
Date: Tue, 25 Mar 2025 15:40:35 +0000 [thread overview]
Message-ID: <174291723501.621610.11595803602695403455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250323100922.59983-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Sun, 23 Mar 2025 11:09:16 +0100 you wrote:
> From: Denis Kirjanov <kirjanov@gmail.com>
>
> Replace vmalloc allocations with kvmalloc since
> kvmalloc is more flexible in memory allocation
>
> Signed-off-by: Denis Kirjanov <kirjanov@gmail.com>
> Reviewed-by: Florian Westphal <fw@strlen.de>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> [...]
Here is the summary with links:
- [net-next,1/7] netfilter: xt_hashlimit: replace vmalloc calls with kvmalloc
https://git.kernel.org/netdev/net-next/c/ddf8dec6db31
- [net-next,2/7] netfilter: conntrack: Bound nf_conntrack sysctl writes
https://git.kernel.org/netdev/net-next/c/8b6861390ffe
- [net-next,3/7] netfilter: fib: avoid lookup if socket is available
https://git.kernel.org/netdev/net-next/c/eaaff9b6702e
- [net-next,4/7] netfilter: nfnetlink_queue: Initialize ctx to avoid memory allocation error
https://git.kernel.org/netdev/net-next/c/778b09d91baa
- [net-next,5/7] netfilter: xtables: Use strscpy() instead of strscpy_pad()
https://git.kernel.org/netdev/net-next/c/3b4aff61ca5d
- [net-next,6/7] netfilter: socket: Lookup orig tuple for IPv6 SNAT
https://git.kernel.org/netdev/net-next/c/932b32ffd760
- [net-next,7/7] netfilter: nf_tables: Only use nf_skip_indirect_calls() when MITIGATION_RETPOLINE
https://git.kernel.org/netdev/net-next/c/e3a4182edd1a
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:[~2025-03-25 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 10:09 [PATCH net-next 0/7] Netfilter updates for net-next Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 1/7] netfilter: xt_hashlimit: replace vmalloc calls with kvmalloc Pablo Neira Ayuso
2025-03-25 15:40 ` patchwork-bot+netdevbpf [this message]
2025-03-23 10:09 ` [PATCH net-next 2/7] netfilter: conntrack: Bound nf_conntrack sysctl writes Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 3/7] netfilter: fib: avoid lookup if socket is available Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 4/7] netfilter: nfnetlink_queue: Initialize ctx to avoid memory allocation error Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 5/7] netfilter: xtables: Use strscpy() instead of strscpy_pad() Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 6/7] netfilter: socket: Lookup orig tuple for IPv6 SNAT Pablo Neira Ayuso
2025-03-23 10:09 ` [PATCH net-next 7/7] netfilter: nf_tables: Only use nf_skip_indirect_calls() when MITIGATION_RETPOLINE Pablo Neira Ayuso
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=174291723501.621610.11595803602695403455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
/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.