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, petrm@nvidia.com
Subject: Re: [PATCH net-next 0/3] net: more heap allocation and split of rtnl_newlink()
Date: Mon, 02 May 2022 13:30:11 +0000 [thread overview]
Message-ID: <165149821176.2157.6275685774105765145.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220429235508.268349-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 29 Apr 2022 16:55:05 -0700 you wrote:
> Small refactoring of rtnl_newlink() to fix a stack usage warning
> and make the function shorter.
>
> Jakub Kicinski (3):
> rtnl: allocate more attr tables on the heap
> rtnl: split __rtnl_newlink() into two functions
> rtnl: move rtnl_newlink_create()
>
> [...]
Here is the summary with links:
- [net-next,1/3] rtnl: allocate more attr tables on the heap
https://git.kernel.org/netdev/net-next/c/c92bf26ccebc
- [net-next,2/3] rtnl: split __rtnl_newlink() into two functions
https://git.kernel.org/netdev/net-next/c/63105e83987a
- [net-next,3/3] rtnl: move rtnl_newlink_create()
https://git.kernel.org/netdev/net-next/c/02839cc8d72b
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-05-02 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 23:55 [PATCH net-next 0/3] net: more heap allocation and split of rtnl_newlink() Jakub Kicinski
2022-04-29 23:55 ` [PATCH net-next 1/3] rtnl: allocate more attr tables on the heap Jakub Kicinski
2022-04-30 7:32 ` Kalle Valo
2022-04-29 23:55 ` [PATCH net-next 2/3] rtnl: split __rtnl_newlink() into two functions Jakub Kicinski
2022-04-29 23:55 ` [PATCH net-next 3/3] rtnl: move rtnl_newlink_create() Jakub Kicinski
2022-05-02 13:30 ` 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=165149821176.2157.6275685774105765145.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 \
--cc=petrm@nvidia.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.