public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Alexis_Lothor=C3=A9_=3Calexis=2Elothore=40bootlin=2Ecom=3E?=@ci.codeaurora.org
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, linux-renesas-soc@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	thomas.petazzoni@bootlin.com, herve.codina@bootlin.com,
	miquel.raynal@bootlin.com, milan.stevanovic@se.com,
	jimmy.lalande@se.com, pascal.eberhard@se.com
Subject: Re: [PATCH net v3 0/3] net: dsa: rzn1-a5psw: fix STP states handling
Date: Sat, 13 May 2023 16:30:21 +0000	[thread overview]
Message-ID: <168399542140.7347.2797429777879901839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230512072712.82694-1-alexis.lothore@bootlin.com>

Hello:

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

On Fri, 12 May 2023 09:27:09 +0200 you wrote:
> From: Alexis Lothoré <alexis.lothore@bootlin.com>
> 
> This small series fixes STP support and while adding a new function to
> enable/disable learning, use that to disable learning on standalone ports
> at switch setup as reported by Vladimir Oltean.
> 
> This series was initially submitted on net-next by Clement Leger, but some
> career evolutions has made him hand me over those topics.
> Also, this new revision is submitted on net instead of net-next for V1
> based on Vladimir Oltean's suggestion
> 
> [...]

Here is the summary with links:
  - [net,v3,1/3] net: dsa: rzn1-a5psw: enable management frames for CPU port
    https://git.kernel.org/netdev/net/c/9e4b45f20c5a
  - [net,v3,2/3] net: dsa: rzn1-a5psw: fix STP states handling
    https://git.kernel.org/netdev/net/c/ebe9bc509527
  - [net,v3,3/3] net: dsa: rzn1-a5psw: disable learning for standalone ports
    https://git.kernel.org/netdev/net/c/ec52b69c046a

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-05-13 16:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  7:27 [PATCH net v3 0/3] net: dsa: rzn1-a5psw: fix STP states handling alexis.lothore
2023-05-12  7:27 ` [PATCH net v3 1/3] net: dsa: rzn1-a5psw: enable management frames for CPU port alexis.lothore
2023-05-12 14:20   ` Piotr Raczynski
2023-05-12  7:27 ` [PATCH net v3 2/3] net: dsa: rzn1-a5psw: fix STP states handling alexis.lothore
2023-05-12  7:27 ` [PATCH net v3 3/3] net: dsa: rzn1-a5psw: disable learning for standalone ports alexis.lothore
2023-05-12 15:43   ` Piotr Raczynski
2023-05-13 16:30 ` 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=168399542140.7347.2797429777879901839.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc==?utf-8?q?Alexis_Lothor=C3=A9_=3Calexis=2Elothore=40bootlin=2Ecom=3E?=@ci.codeaurora.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=herve.codina@bootlin.com \
    --cc=jimmy.lalande@se.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=milan.stevanovic@se.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=pascal.eberhard@se.com \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox