public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sverdlin@ci.codeaurora.org, Alexander <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, olteanv@gmail.com, andrew@lunn.ch,
	f.fainelli@gmail.com, linux-kernel@vger.kernel.org,
	privat@egil-hjelmeland.no
Subject: Re: [PATCH] net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
Date: Fri, 02 Jun 2023 04:50:19 +0000	[thread overview]
Message-ID: <168568141993.21492.6855399273666602310.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230531143826.477267-1-alexander.sverdlin@siemens.com>

Hello:

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

On Wed, 31 May 2023 16:38:26 +0200 you wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> 
> LAN9303 doesn't associate FDB (ALR) entries with VLANs, it has just one
> global Address Logic Resolution table [1].
> 
> Ignore VID in port_fdb_{add|del} methods, go on with the global table. This
> is the same semantics as hellcreek or RZ/N1 implement.
> 
> [...]

Here is the summary with links:
  - net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
    https://git.kernel.org/netdev/net/c/5a59a58ec25d

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



      parent reply	other threads:[~2023-06-02  4:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 14:38 [PATCH] net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods A. Sverdlin
2023-05-31 15:16 ` Vladimir Oltean
2023-05-31 15:20   ` Sverdlin, Alexander
2023-05-31 15:35     ` Vladimir Oltean
2023-06-01  4:41       ` Jakub Kicinski
2023-06-01  8:32         ` Vladimir Oltean
2023-06-02  4:50 ` patchwork-bot+netdevbpf [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=168568141993.21492.6855399273666602310.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Sverdlin@ci.codeaurora.org \
    --cc=alexander.sverdlin@siemens.com \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=privat@egil-hjelmeland.no \
    /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