From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, ayush.sawal@chelsio.com,
andrew+netdev@lunn.ch, dsahern@kernel.org, ncardwell@google.com,
kuniyu@google.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
guwen@linux.alibaba.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-s390@vger.kernel.org, sidraya@linux.ibm.com,
dust.li@linux.alibaba.com
Subject: Re: [PATCH net-next v3 0/6] net: Remove unused function parameters in skbuff.c
Date: Tue, 08 Jul 2025 16:00:21 +0000 [thread overview]
Message-ID: <175199042124.4117860.11392671467837095763.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250702-splice-drop-unused-v3-0-55f68b60d2b7@rbox.co>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 02 Jul 2025 15:38:06 +0200 you wrote:
> Couple of cleanup patches to get rid of unused function parameters around
> skbuff.c, plus little things spotted along the way.
>
> Offshoot of my question in [1], but way more contained. Found by adding
> "-Wunused-parameter -Wno-error" to KBUILD_CFLAGS and grepping for specific
> skbuff.c warnings.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] net: splice: Drop unused @pipe
https://git.kernel.org/netdev/net-next/c/1024f1207161
- [net-next,v3,2/6] net: splice: Drop unused @gfp
https://git.kernel.org/netdev/net-next/c/25489a4f5564
- [net-next,v3,3/6] net: splice: Drop nr_pages_max initialization
(no matching commit)
- [net-next,v3,4/6] net/smc: Drop nr_pages_max initialization
(no matching commit)
- [net-next,v3,5/6] net: skbuff: Drop unused @skb
https://git.kernel.org/netdev/net-next/c/ad0ac6cd9c04
- [net-next,v3,6/6] net: skbuff: Drop unused @skb
https://git.kernel.org/netdev/net-next/c/ab34e14258cd
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-07-08 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 13:38 Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 1/6] net: splice: Drop unused @pipe Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 2/6] net: splice: Drop unused @gfp Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 3/6] net: splice: Drop nr_pages_max initialization Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 4/6] net/smc: " Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 5/6] net: skbuff: Drop unused @skb Michal Luczaj
2025-07-02 13:38 ` [PATCH net-next v3 6/6] " Michal Luczaj
2025-07-08 16: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=175199042124.4117860.11392671467837095763.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=ayush.sawal@chelsio.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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
all inboxes | Powered by JetHome®