[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <164490300956.28678.14688275132424958290.git-patchwork-notify@kernel.org>
Date: Tue, 15 Feb 2022 05:30:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Jon Maloy <jmaloy@...hat.com>
Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
tipc-discussion@...ts.sourceforge.net,
tung.q.nguyen@...tech.com.au, hoang.h.le@...tech.com.au,
tuong.t.lien@...tech.com.au, maloy@...jonn.com, xinl@...hat.com,
ying.xue@...driver.com, parthasarathy.bhuvaragan@...il.com
Subject: Re: [net] tipc: fix wrong publisher node address in link publications
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Sun, 13 Feb 2022 20:38:52 -0500 you wrote:
> From: Jon Maloy <jmaloy@...hat.com>
>
> When a link comes up we add its presence to the name table to make it
> possible for users to subscribe for link up/down events. However, after
> a previous call signature change the binding is wrongly published with
> the peer node as publishing node, instead of the own node as it should
> be. This has the effect that the command 'tipc name table show' will
> list the link binding (service type 2) with node scope and a peer node
> as originator, something that obviously is impossible.
>
> [...]
Here is the summary with links:
- [net] tipc: fix wrong publisher node address in link publications
https://git.kernel.org/netdev/net/c/032062f363b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists