From: patchwork-bot+netdevbpf@kernel.org
To: Guillaume Nault <gnault@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
martin.varghese@nokia.com
Subject: Re: [PATCH net-next 0/2] bareudp: Remove unused code from header file
Date: Mon, 13 Dec 2021 12:50:10 +0000 [thread overview]
Message-ID: <163939981002.30215.2793574527337535525.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1639166064.git.gnault@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 10 Dec 2021 20:56:33 +0100 you wrote:
> 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
>
> [...]
Here is the summary with links:
- [net-next,1/2] bareudp: Remove bareudp_dev_create()
https://git.kernel.org/netdev/net-next/c/614b7a1f28f4
- [net-next,2/2] bareudp: Move definition of struct bareudp_conf to bareudp.c
https://git.kernel.org/netdev/net-next/c/dcdd77ee55a7
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:[~2021-12-13 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 19:56 [PATCH net-next 0/2] bareudp: Remove unused code from header file Guillaume Nault
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 ` 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=163939981002.30215.2793574527337535525.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gnault@redhat.com \
--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 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.