From: patchwork-bot+netdevbpf@kernel.org
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com, olteanv@gmail.com,
tobias@waldekranz.com, kuba@kernel.org, davem@davemloft.net,
vivien.didelot@gmail.com
Subject: Re: [PATCH net-next v2 0/2] net: dsa: mv88e6xxx: remove some 6250-specific methods
Date: Wed, 27 Jan 2021 02:10:11 +0000 [thread overview]
Message-ID: <161171341157.20940.9935214678600398819.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210125150449.115032-1-rasmus.villemoes@prevas.dk>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Mon, 25 Jan 2021 16:04:47 +0100 you wrote:
> v2:
>
> - resend now that the bug-fix patch (87fe04367d84, "net: dsa:
> mv88e6xxx: also read STU state in mv88e6250_g1_vtu_getnext") is in
> net and also merged to net-next.
>
> - include various tags in patch 1.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: dsa: mv88e6xxx: use mv88e6185_g1_vtu_getnext() for the 6250
https://git.kernel.org/netdev/net-next/c/67c9ed1c8809
- [net-next,v2,2/2] net: dsa: mv88e6xxx: use mv88e6185_g1_vtu_loadpurge() for the 6250
https://git.kernel.org/netdev/net-next/c/b28f3f3c3f30
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-01-27 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 15:04 [PATCH net-next v2 0/2] net: dsa: mv88e6xxx: remove some 6250-specific methods Rasmus Villemoes
2021-01-25 15:04 ` [PATCH net-next v2 1/2] net: dsa: mv88e6xxx: use mv88e6185_g1_vtu_getnext() for the 6250 Rasmus Villemoes
2021-01-26 21:53 ` Vladimir Oltean
2021-01-25 15:04 ` [PATCH net-next v2 2/2] net: dsa: mv88e6xxx: use mv88e6185_g1_vtu_loadpurge() " Rasmus Villemoes
2021-01-26 21:55 ` Vladimir Oltean
2021-01-27 2:10 ` 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=161171341157.20940.9935214678600398819.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=tobias@waldekranz.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 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.