All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, petrm@nvidia.com,
	mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/8] mlxsw: Various updates
Date: Wed, 04 May 2022 10:30:13 +0000	[thread overview]
Message-ID: <165166021359.27992.10606056306672238609.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220504062909.536194-1-idosch@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed,  4 May 2022 09:29:01 +0300 you wrote:
> Patches #1-#3 add missing topology diagrams in selftests and perform
> small cleanups.
> 
> Patches #4-#5 make small adjustments in QoS configuration. See detailed
> description in the commit messages.
> 
> Patches #6-#8 reduce the number of background EMAD transactions. The
> driver periodically queries the device (via EMAD transactions) about
> updates that cannot happen in certain situations. This can negatively
> impact the latency of time critical transactions, as the device is busy
> processing other transactions.
> 
> [...]

Here is the summary with links:
  - [net-next,1/8] selftests: mlxsw: bail_on_lldpad before installing the cleanup trap
    https://git.kernel.org/netdev/net-next/c/18d2c710e5df
  - [net-next,2/8] selftests: router_vid_1: Add a diagram, fix coding style
    https://git.kernel.org/netdev/net-next/c/5ade50e2df2b
  - [net-next,3/8] selftests: router.sh: Add a diagram
    https://git.kernel.org/netdev/net-next/c/faa7521add89
  - [net-next,4/8] mlxsw: spectrum_dcb: Do not warn about priority changes
    https://git.kernel.org/netdev/net-next/c/b6b584562cbe
  - [net-next,5/8] mlxsw: Treat LLDP packets as control
    https://git.kernel.org/netdev/net-next/c/0106668cd2f9
  - [net-next,6/8] mlxsw: spectrum_acl: Do not report activity for multicast routes
    https://git.kernel.org/netdev/net-next/c/d1314096fbe9
  - [net-next,7/8] mlxsw: spectrum_switchdev: Only query FDB notifications when necessary
    https://git.kernel.org/netdev/net-next/c/b8950003849d
  - [net-next,8/8] mlxsw: spectrum_router: Only query neighbour activity when necessary
    https://git.kernel.org/netdev/net-next/c/cff9437605d5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-05-04 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  6:29 [PATCH net-next 0/8] mlxsw: Various updates Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 1/8] selftests: mlxsw: bail_on_lldpad before installing the cleanup trap Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 2/8] selftests: router_vid_1: Add a diagram, fix coding style Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 3/8] selftests: router.sh: Add a diagram Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 4/8] mlxsw: spectrum_dcb: Do not warn about priority changes Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 5/8] mlxsw: Treat LLDP packets as control Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 6/8] mlxsw: spectrum_acl: Do not report activity for multicast routes Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 7/8] mlxsw: spectrum_switchdev: Only query FDB notifications when necessary Ido Schimmel
2022-05-04  6:29 ` [PATCH net-next 8/8] mlxsw: spectrum_router: Only query neighbour activity " Ido Schimmel
2022-05-04 10:30 ` patchwork-bot+netdevbpf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-08 12:44 [PATCH net-next 0/8] mlxsw: Various updates Ido Schimmel
2021-06-08 21:50 ` patchwork-bot+netdevbpf

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=165166021359.27992.10606056306672238609.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.