From: patchwork-bot+netdevbpf@kernel.org
To: Jon Maloy <jmaloy@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
tipc-discussion@lists.sourceforge.net,
tung.q.nguyen@dektech.com.au, hoang.h.le@dektech.com.au,
tuong.t.lien@dektech.com.au, maloy@donjonn.com, xinl@redhat.com,
ying.xue@windriver.com, parthasarathy.bhuvaragan@gmail.com
Subject: Re: [v2,net] tipc: fix wrong notification node addresses
Date: Thu, 17 Feb 2022 05:20:10 +0000 [thread overview]
Message-ID: <164507521078.4843.2149091000529160346.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220216020009.3404578-1-jmaloy@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Feb 2022 21:00:09 -0500 you wrote:
> From: Jon Maloy <jmaloy@redhat.com>
>
> The previous bug fix had an unfortunate side effect that broke
> distribution of binding table entries between nodes. The updated
> tipc_sock_addr struct is also used further down in the same
> function, and there the old value is still the correct one.
>
> [...]
Here is the summary with links:
- [v2,net] tipc: fix wrong notification node addresses
https://git.kernel.org/netdev/net/c/c08e58438d4a
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-02-17 5:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 2:00 [v2,net] tipc: fix wrong notification node addresses jmaloy
2022-02-16 7:08 ` Leon Romanovsky
2022-02-16 15:12 ` Jon Maloy
2022-02-16 16:12 ` Leon Romanovsky
2022-02-17 5:20 ` 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=164507521078.4843.2149091000529160346.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hoang.h.le@dektech.com.au \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=parthasarathy.bhuvaragan@gmail.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--cc=tuong.t.lien@dektech.com.au \
--cc=xinl@redhat.com \
--cc=ying.xue@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).