From: Guillaume Nault <gnault@redhat.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, Martin Varghese <martin.varghese@nokia.com>
Subject: [PATCH net-next 0/2] bareudp: Remove unused code from header file
Date: Fri, 10 Dec 2021 20:56:33 +0100 [thread overview]
Message-ID: <cover.1639166064.git.gnault@redhat.com> (raw)
Stop exporting unused functions and structures in bareudp.h. The only
piece of bareudp.h that is actually used is netif_is_bareudp(). The
rest can be moved to bareudp.c or even dropped entirely.
Guillaume Nault (2):
bareudp: Remove bareudp_dev_create()
bareudp: Move definition of struct bareudp_conf to bareudp.c
drivers/net/bareudp.c | 41 +++++++----------------------------------
include/net/bareudp.h | 13 +------------
2 files changed, 8 insertions(+), 46 deletions(-)
--
2.21.3
next reply other threads:[~2021-12-10 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 19:56 Guillaume Nault [this message]
2021-12-10 19:56 ` [PATCH net-next 1/2] bareudp: Remove bareudp_dev_create() Guillaume Nault
2021-12-10 19:56 ` [PATCH net-next 2/2] bareudp: Move definition of struct bareudp_conf to bareudp.c Guillaume Nault
2021-12-13 12:50 ` [PATCH net-next 0/2] bareudp: Remove unused code from header file 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=cover.1639166064.git.gnault@redhat.com \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.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 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).