From: David Ahern <dsahern@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Stanislav Fomichev <sdf@google.com>
Subject: Re: [PATCH net-next] net: move gso declarations and functions to their own files
Date: Fri, 9 Jun 2023 12:55:42 -0600 [thread overview]
Message-ID: <20230609185542.GA23541@u2004-local> (raw)
In-Reply-To: <20230608191738.3947077-1-edumazet@google.com>
On Thu, Jun 08, 2023 at 07:17:37PM +0000, Eric Dumazet 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>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-06-09 18:55 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 [this message]
2023-06-10 7:21 ` patchwork-bot+netdevbpf
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=20230609185542.GA23541@u2004-local \
--to=dsahern@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).