On Thu, Apr 30, 2026 at 4:23 AM Takeru Hayasaka <[email protected]> wrote:
> Previously fdb/show required exactly one bridge argument. This > change allows specifying multiple bridge names in a single call, > reducing the number of unixctl round-trips for clients that need > to poll FDB entries across many bridges (e.g. EVPN agents managing > multiple VNIs). > > The output format is now consistent regardless of how many bridges > are passed. Text output always prefixes each bridge's table with > a "bridge <name>" header line. JSON output is always an array of > objects, each containing "bridge" and "entries" keys. This is a > backward-incompatible change for the single-bridge case but keeps > the per-bridge formatting fully encapsulated in the helper > functions. > > Signed-off-by: Takeru Hayasaka <[email protected]> > --- Looks good to me! Acked-by: Mike Pattrick <[email protected]> _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
