From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com, sdf@google.com
Subject: Re: [PATCH net-next] net: move gso declarations and functions to their own files
Date: Sat, 10 Jun 2023 07:21:34 +0000 [thread overview]
Message-ID: <168638169468.9909.16606138404983687177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230608191738.3947077-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Jun 2023 19:17:37 +0000 you wrote:
> Move declarations into include/net/gso.h and code into net/core/gso.c
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Stanislav Fomichev <sdf@google.com>
> ---
> drivers/net/ethernet/broadcom/tg3.c | 1 +
> .../net/ethernet/myricom/myri10ge/myri10ge.c | 1 +
> drivers/net/ethernet/sfc/siena/tx_common.c | 1 +
> drivers/net/ethernet/sfc/tx_common.c | 1 +
> drivers/net/tap.c | 1 +
> drivers/net/usb/r8152.c | 1 +
> drivers/net/wireguard/device.c | 1 +
> drivers/net/wireless/intel/iwlwifi/mvm/tx.c | 1 +
> include/linux/netdevice.h | 26 +-
> include/linux/skbuff.h | 71 -----
> include/net/gro.h | 1 +
> include/net/gso.h | 109 +++++++
> include/net/udp.h | 1 +
> net/core/Makefile | 2 +-
> net/core/dev.c | 70 +----
> net/core/gro.c | 59 +---
> net/core/gso.c | 273 ++++++++++++++++++
> net/core/skbuff.c | 142 +--------
> net/ipv4/af_inet.c | 1 +
> net/ipv4/esp4_offload.c | 1 +
> net/ipv4/gre_offload.c | 1 +
> net/ipv4/ip_output.c | 1 +
> net/ipv4/tcp_offload.c | 1 +
> net/ipv4/udp.c | 1 +
> net/ipv4/udp_offload.c | 1 +
> net/ipv6/esp6_offload.c | 1 +
> net/ipv6/ip6_offload.c | 1 +
> net/ipv6/ip6_output.c | 1 +
> net/ipv6/udp_offload.c | 1 +
> net/mac80211/tx.c | 1 +
> net/mpls/af_mpls.c | 1 +
> net/mpls/mpls_gso.c | 1 +
> net/netfilter/nf_flow_table_ip.c | 1 +
> net/netfilter/nfnetlink_queue.c | 1 +
> net/nsh/nsh.c | 1 +
> net/openvswitch/actions.c | 1 +
> net/openvswitch/datapath.c | 1 +
> net/sched/act_police.c | 1 +
> net/sched/sch_cake.c | 1 +
> net/sched/sch_netem.c | 1 +
> net/sched/sch_taprio.c | 1 +
> net/sched/sch_tbf.c | 1 +
> net/sctp/offload.c | 1 +
> net/xfrm/xfrm_device.c | 1 +
> net/xfrm/xfrm_interface_core.c | 1 +
> net/xfrm/xfrm_output.c | 1 +
> 46 files changed, 425 insertions(+), 365 deletions(-)
> create mode 100644 include/net/gso.h
> create mode 100644 net/core/gso.c
Here is the summary with links:
- [net-next] net: move gso declarations and functions to their own files
https://git.kernel.org/netdev/net-next/c/d457a0e329b0
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:[~2023-06-10 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 19:17 [PATCH net-next] net: move gso declarations and functions to their own files Eric Dumazet
2023-06-09 13:19 ` Simon Horman
2023-06-09 18:55 ` David Ahern
2023-06-10 7:21 ` 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=168638169468.9909.16606138404983687177.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.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).