public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, Andy Gospodarek <andy@greyhouse.net>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Ido Schimmel <idosch@nvidia.com>,
	Jiri Pirko <jiri@resnulli.us>, Amit Cohen <amcohen@nvidia.com>
Subject: Re: [PATCHv3 net-next] bonding: 3ad: send ifinfo notify when mux state changed
Date: Thu, 11 Jul 2024 11:12:52 +0800	[thread overview]
Message-ID: <Zo9NtDv8ULtbaJ_k@Laptop-X1> (raw)
In-Reply-To: <ZoOzge5Xn42QtG91@Laptop-X1>

On Tue, Jul 02, 2024 at 04:00:06PM +0800, Hangbin Liu wrote:
> > 	Looking at the current notifications in bonding, I wonder if it
> > would be sufficient to add the desired information to what
> > bond_lower_state_changed() sends, rather than trying to shoehorn in
> > another rtnl_trylock() gizmo.
> 
> I'm not sure if the LACP state count for lower state. What do you think of
> my previous draft patch[1] that replied to you.
> 
> [1] https://lore.kernel.org/netdev/Zn0iI3SPdRkmfnS1@Laptop-X1/

Hi Jay,

Any comments?

Thanks
Hangbin

  reply	other threads:[~2024-07-11  3:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  7:51 [PATCHv3 net-next] bonding: 3ad: send ifinfo notify when mux state changed Hangbin Liu
2024-06-26  8:22 ` Nikolay Aleksandrov
2024-06-26 15:30 ` Jay Vosburgh
2024-06-26 21:53 ` Jakub Kicinski
2024-06-27  0:06   ` Jay Vosburgh
2024-06-27  8:26     ` Hangbin Liu
2024-06-27  8:29       ` Nikolay Aleksandrov
2024-06-27 10:05         ` Hangbin Liu
2024-06-27 10:33           ` Nikolay Aleksandrov
2024-06-27 13:17             ` Hangbin Liu
2024-06-27 14:12               ` Nikolay Aleksandrov
2024-06-27 14:24               ` Jay Vosburgh
2024-06-28  3:10                 ` Hangbin Liu
2024-06-28  7:04                   ` Nikolay Aleksandrov
2024-06-28  7:22                     ` Nikolay Aleksandrov
2024-06-28  9:55                       ` Hangbin Liu
2024-06-28 23:36                         ` Jay Vosburgh
2024-07-02  8:00                           ` Hangbin Liu
2024-07-11  3:12                             ` Hangbin Liu [this message]
2024-07-19  6:45                               ` Hangbin Liu
2024-07-29  7:43                                 ` Hangbin Liu

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=Zo9NtDv8ULtbaJ_k@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=amcohen@nvidia.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    /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