[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL+tcoBJOuLCr1tvFr6cMbTjBOO_JRW__h4YN90Bxg-TComtsQ@mail.gmail.com>
Date: Tue, 2 Dec 2025 09:54:43 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: Tonghao Zhang <tonghao@...aicloud.com>
Cc: netdev@...r.kernel.org, Jay Vosburgh <jv@...sburgh.net>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
Jonathan Corbet <corbet@....net>, Andrew Lunn <andrew+netdev@...n.ch>,
Nikolay Aleksandrov <razor@...ckwall.org>, Hangbin Liu <liuhangbin@...il.com>
Subject: Re: [PATCH net-next v3 2/4] net: bonding: move bond_should_notify_peers,
e.g. into rtnl lock block
On Sun, Nov 30, 2025 at 3:49 PM Tonghao Zhang <tonghao@...aicloud.com> wrote:
>
> This patch trys to fix the possible peer notify event loss.
s/trys/tries
Is this patch standalone as a fix since you mentioned 'fix' as above?
If so, then you would add "Fixes: "" <>" tag to manifest which commit
brought the issue and then post it separately to the net tree. It
would be helpful for the stable team to backport fixes.
Thanks,
Jason
Powered by blists - more mailing lists