From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id F1471C433FE for ; Thu, 17 Feb 2022 05:20:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234143AbiBQFUf (ORCPT ); Thu, 17 Feb 2022 00:20:35 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:39562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229523AbiBQFUd (ORCPT ); Thu, 17 Feb 2022 00:20:33 -0500 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8545A2A598F for ; Wed, 16 Feb 2022 21:20:14 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id A8478CE2A7E for ; Thu, 17 Feb 2022 05:20:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id DDDAAC340EB; Thu, 17 Feb 2022 05:20:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1645075210; bh=G1QZvwcruw6oCbc/jrtCbpvbJ+HUW6ilSH9PlZseKv4=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=goLfzTDrDk+qrZi2Hj2j3mphEtmEP4h9UnbXZQMGpPO9iXYE59ISbStNwoslQrhqU 0iQ9a4S1RWfN3mUw+WkPCi+cZfYckRMGrqOV5I382QXIg8ag69cP9WkdiaAUAgG2DZ faxsMlG+SA4nw72P8LPPFz3yBREcDq1YwVWwFZrFf+tdcVLCb3pcow6Ea4ppLXoDJ4 uOeF1OprMDvGmc7+qJv7BSO1sQyk2RDEs0LD05KcrCcRRGkrgdkPIg4OaZh9zTOiij RCafY7RZjidlCjBcV1NDWlusYweknGqLvKzLheanvoxNxJ7nVhL3krZw9QkcHbfLrT YpCoTS3abeG4Q== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id C03E0E6D447; Thu, 17 Feb 2022 05:20:10 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [v2,net] tipc: fix wrong notification node addresses From: patchwork-bot+netdevbpf@kernel.org Message-Id: <164507521078.4843.2149091000529160346.git-patchwork-notify@kernel.org> Date: Thu, 17 Feb 2022 05:20:10 +0000 References: <20220216020009.3404578-1-jmaloy@redhat.com> In-Reply-To: <20220216020009.3404578-1-jmaloy@redhat.com> To: Jon Maloy 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 Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello: This patch was applied to netdev/net.git (master) by Jakub Kicinski : On Tue, 15 Feb 2022 21:00:09 -0500 you wrote: > From: Jon Maloy > > 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