On 23 Feb 15:39, Saeed Mahameed wrote:
From: Saeed Mahameed <saeedm@xxxxxxxxxx> Hi Dave, Jakub and Jason, v1->v2: - Fix typo in the 1st patch's title The following PR includes updates to mlx5-next branch: Headlines: ========== 1) Jakub cleans up unused static inline functions 2) I did some low level firmware command interface return status changes to provide the caller with full visibility on the error/status returned by the Firmware. 3) Use the new command interface in RDMA DEVX usecases to avoid flooding dmesg with some "expected" user error prone use cases. 4) Moshe also uses the new command interface to grab the specific error code from MFRL register command to provide the exact error reason for why SW reset couldn't perform internally in FW. 5) From Mark Bloch: Lag, drop packets in hardware when possible In active-backup mode the inactive interface's packets are dropped by the bond device. In switchdev where TC rules are offloaded to the FDB this can lead to packets being hit in the FDB where without offload they would have been dropped before reaching TC rules in the kernel. Create a drop rule to make sure packets on inactive ports are dropped before reaching the FDB. Listen on NETDEV_CHANGEUPPER / NETDEV_CHANGEINFODATA events and record the inactive state and offload accordingly. ========== Please pull and let me know if there's any problem. The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07: Linux 5.17-rc1 (2022-01-23 10:12:53 +0200) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next for you to fetch changes up to 45fee8edb4b333af79efad7a99de51718ebda94b: net/mlx5: Add clarification on sync reset failure (2022-02-23 15:21:59 -0800)
Dave, Jakub, I expecting this to be pulled into net-next, let me know if I did something wrong, I see the series is marked as "Awaiting upstream" in patchworks.
