From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?=C3=81lvaro_Fern=C3=A1ndez_Rojas_=3Cnoltari=40gmail=2Ecom=3E?=@ci.codeaurora.org
Cc: jonas.gorski@gmail.com, f.fainelli@gmail.com, andrew@lunn.ch,
vivien.didelot@gmail.com, olteanv@gmail.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] net: dsa: b53: support legacy tags
Date: Wed, 17 Mar 2021 19:30:10 +0000 [thread overview]
Message-ID: <161600941050.18835.372070166540076281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210317102927.25605-1-noltari@gmail.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 17 Mar 2021 11:29:25 +0100 you wrote:
> Legacy Broadcom tags are needed for older switches.
>
> Álvaro Fernández Rojas (2):
> net: dsa: tag_brcm: add support for legacy tags
> net: dsa: b53: support legacy tags
>
> drivers/net/dsa/b53/Kconfig | 1 +
> drivers/net/dsa/b53/b53_common.c | 12 ++--
> include/net/dsa.h | 2 +
> net/dsa/Kconfig | 7 ++
> net/dsa/tag_brcm.c | 107 ++++++++++++++++++++++++++++++-
> 5 files changed, 121 insertions(+), 8 deletions(-)
Here is the summary with links:
- [v2,net-next,1/2] net: dsa: tag_brcm: add support for legacy tags
https://git.kernel.org/netdev/net-next/c/964dbf186eaa
- [v2,net-next,2/2] net: dsa: b53: support legacy tags
https://git.kernel.org/netdev/net-next/c/46c5176c586c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-17 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 10:29 [PATCH v2 net-next 0/2] net: dsa: b53: support legacy tags Álvaro Fernández Rojas
2021-03-17 10:29 ` [PATCH v2 net-next 1/2] net: dsa: tag_brcm: add support for " Álvaro Fernández Rojas
2021-03-17 10:29 ` [PATCH v2 net-next 2/2] net: dsa: b53: support " Álvaro Fernández Rojas
2021-03-17 19: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=161600941050.18835.372070166540076281.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?=C3=81lvaro_Fern=C3=A1ndez_Rojas_=3Cnoltari=40gmail=2Ecom=3E?=@ci.codeaurora.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.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