From: patchwork-bot+netdevbpf@kernel.org
To: Yue Haibing <yuehaibing@huawei.com>
Cc: jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
lucien.xin@gmail.com, netdev@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next] tipc: Remove unused function declarations
Date: Thu, 03 Aug 2023 11:10:20 +0000 [thread overview]
Message-ID: <169106102071.8585.16493259766116573750.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230802034659.39840-1-yuehaibing@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 2 Aug 2023 11:46:59 +0800 you wrote:
> Commit d50ccc2d3909 ("tipc: add 128-bit node identifier") declared but never
> implemented tipc_node_id2hash().
> Also commit 5c216e1d28c8 ("tipc: Allow run-time alteration of default link settings")
> never implemented tipc_media_set_priority() and tipc_media_set_window(),
> commit cad2929dc432 ("tipc: update a binding service via broadcast") only declared
> tipc_named_bcast().
>
> [...]
Here is the summary with links:
- [net-next] tipc: Remove unused function declarations
https://git.kernel.org/netdev/net-next/c/c956910d5af1
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:[~2023-08-03 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 3:46 [PATCH net-next] tipc: Remove unused function declarations Yue Haibing
2023-08-02 15:09 ` Simon Horman
2023-08-03 11:10 ` 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=169106102071.8585.16493259766116573750.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.com \
--cc=yuehaibing@huawei.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.