linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sean Anderson <sean.anderson@linux.dev>
Cc: radhey.shyam.pandey@amd.com, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, edumazet@google.com,
	michal.simek@amd.com, andrew@lunn.ch, daniel@iogearbox.net,
	davem@davemloft.net, kuba@kernel.org,
	linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next v3 0/5] net: xilinx: axienet: Multicast fixes and improvements
Date: Thu, 22 Aug 2024 20:10:39 +0000	[thread overview]
Message-ID: <172435743953.2469005.10916421971671295339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822154059.1066595-1-sean.anderson@linux.dev>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 22 Aug 2024 11:40:54 -0400 you wrote:
> This series has a few small patches improving the handling of multicast
> addresses. In particular, it makes the driver a whole lot less spammy,
> and adjusts things so we aren't in promiscuous mode when we have more
> than four multicast addresses (a common occurance on modern systems).
> 
> As the hardware has a 4-entry CAM, the ideal method would be to "pack"
> multiple addresses into one CAM entry. Something like:
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/5] net: xilinx: axienet: Always disable promiscuous mode
    https://git.kernel.org/netdev/net/c/4ae738dfef2c
  - [net-next,v3,2/5] net: xilinx: axienet: Fix dangling multicast addresses
    https://git.kernel.org/netdev/net/c/797a68c9de0f
  - [net-next,v3,3/5] net: xilinx: axienet: Don't print if we go into promiscuous mode
    (no matching commit)
  - [net-next,v3,4/5] net: xilinx: axienet: Don't set IFF_PROMISC in ndev->flags
    (no matching commit)
  - [net-next,v3,5/5] net: xilinx: axienet: Support IFF_ALLMULTI
    (no matching commit)

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




  parent reply	other threads:[~2024-08-22 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 15:40 [PATCH net-next v3 0/5] net: xilinx: axienet: Multicast fixes and improvements Sean Anderson
2024-08-22 15:40 ` [PATCH net-next v3 1/5] net: xilinx: axienet: Always disable promiscuous mode Sean Anderson
2024-08-22 15:40 ` [PATCH net-next v3 2/5] net: xilinx: axienet: Fix dangling multicast addresses Sean Anderson
2024-08-22 15:40 ` [PATCH net-next v3 3/5] net: xilinx: axienet: Don't print if we go into promiscuous mode Sean Anderson
2024-08-22 15:40 ` [PATCH net-next v3 4/5] net: xilinx: axienet: Don't set IFF_PROMISC in ndev->flags Sean Anderson
2024-08-22 15:40 ` [PATCH net-next v3 5/5] net: xilinx: axienet: Support IFF_ALLMULTI Sean Anderson
2024-08-22 20:10 ` patchwork-bot+netdevbpf [this message]
2024-08-26 17:00 ` [PATCH net-next v3 0/5] net: xilinx: axienet: Multicast fixes and improvements 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=172435743953.2469005.10916421971671295339.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=radhey.shyam.pandey@amd.com \
    --cc=sean.anderson@linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).