From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [PATCH net-next 0/3] net: create a net/core/ internal header
Date: Fri, 08 Apr 2022 04:00:13 +0000 [thread overview]
Message-ID: <164939041346.25172.3549599788418547609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220406213754.731066-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 Apr 2022 14:37:51 -0700 you wrote:
> We are adding stuff to netdevice.h which really should be
> local to net/core/. Create a net/core/dev.h header and use it.
> Minor cleanups precede.
>
> Jakub Kicinski (3):
> net: hyperv: remove use of bpf_op_t
> net: unexport a handful of dev_* functions
> net: extract a few internals from netdevice.h
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: hyperv: remove use of bpf_op_t
https://git.kernel.org/netdev/net-next/c/e416531f0459
- [net-next,2/3] net: unexport a handful of dev_* functions
https://git.kernel.org/netdev/net-next/c/2cc6cdd44a16
- [net-next,3/3] net: extract a few internals from netdevice.h
https://git.kernel.org/netdev/net-next/c/6264f58ca0e5
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:[~2022-04-08 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 21:37 [PATCH net-next 0/3] net: create a net/core/ internal header Jakub Kicinski
2022-04-06 21:37 ` [PATCH net-next 1/3] net: hyperv: remove use of bpf_op_t Jakub Kicinski
2022-04-07 13:12 ` Wei Liu
2022-04-06 21:37 ` [PATCH net-next 2/3] net: unexport a handful of dev_* functions Jakub Kicinski
2022-04-06 21:37 ` [PATCH net-next 3/3] net: extract a few internals from netdevice.h Jakub Kicinski
2022-04-08 4: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=164939041346.25172.3549599788418547609.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.