public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hans Schultz <netdev@kapio-technology•com>
To: Vladimir Oltean <vladimir.oltean@nxp•com>
Cc: netdev@vger•kernel.org, Jakub Kicinski <kuba@kernel•org>,
	"David S. Miller" <davem@davemloft•net>,
	Eric Dumazet <edumazet@google•com>,
	Paolo Abeni <pabeni@redhat•com>, Ido Schimmel <idosch@nvidia•com>,
	Roopa Prabhu <roopa@nvidia•com>,
	Nikolay Aleksandrov <razor@blackwall•org>,
	Ivan Vecera <ivecera@redhat•com>, Jiri Pirko <jiri@resnulli•us>,
	Jesse Brandeburg <jesse.brandeburg@intel•com>,
	bridge@lists•linux-foundation.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH v2 net] net: bridge: switchdev: don't notify FDB entries with "master dynamic"
Date: Mon, 24 Apr 2023 17:37:07 +0200	[thread overview]
Message-ID: <87h6t51ecc.fsf@kapio-technology.com> (raw)
In-Reply-To: <20230424122631.d7kwfwmlwvqjo3pz@skbuf>

On Mon, Apr 24, 2023 at 15:26, Vladimir Oltean <vladimir.oltean@nxp•com> wrote:
>
> Obviously we have not reached the end of that plan, and net-next is closed now.

Seems to me that net-next is open. Maybe it will close soon.

      parent reply	other threads:[~2023-04-24 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 15:59 [PATCH v2 net] net: bridge: switchdev: don't notify FDB entries with "master dynamic" Vladimir Oltean
2023-04-19 12:49 ` Ido Schimmel
2023-04-20  6:23 ` Ido Schimmel
2023-04-20  7:50 ` patchwork-bot+netdevbpf
2023-04-23  8:47 ` Hans Schultz
2023-04-24 12:26   ` Vladimir Oltean
2023-04-24 15:33     ` Hans Schultz
2023-04-24 15:37     ` Hans Schultz [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=87h6t51ecc.fsf@kapio-technology.com \
    --to=netdev@kapio-technology$(echo .)com \
    --cc=bridge@lists$(echo .)linux-foundation.org \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=idosch@nvidia$(echo .)com \
    --cc=ivecera@redhat$(echo .)com \
    --cc=jesse.brandeburg@intel$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=razor@blackwall$(echo .)org \
    --cc=roopa@nvidia$(echo .)com \
    --cc=vladimir.oltean@nxp$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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