From: patchwork-bot+netdevbpf@kernel.org
To: Robert Marko <robimarko@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: dsa: mv88e6xxx: add Amethyst specific SMI GPIO function
Date: Thu, 29 Feb 2024 09:30:29 +0000 [thread overview]
Message-ID: <170919902947.26621.622513714154438592.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240227175457.2766628-1-robimarko@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 27 Feb 2024 18:54:20 +0100 you wrote:
> Amethyst family (MV88E6191X/6193X/6393X) has a simplified SMI GPIO setting
> via the Scratch and Misc register so it requires family specific function.
>
> In the v1 review, Andrew pointed out that it would make sense to rename the
> existing mv88e6xxx_g2_scratch_gpio_set_smi as it only works on the MV6390
> family.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] net: dsa: mv88e6xxx: rename mv88e6xxx_g2_scratch_gpio_set_smi
https://git.kernel.org/netdev/net-next/c/5c5b0c444be3
- [net-next,v2,2/2] net: dsa: mv88e6xxx: add Amethyst specific SMI GPIO function
https://git.kernel.org/netdev/net-next/c/e3ab3267a0bb
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:[~2024-02-29 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:54 [PATCH net-next v2 0/2] net: dsa: mv88e6xxx: add Amethyst specific SMI GPIO function Robert Marko
2024-02-27 17:54 ` [PATCH net-next v2 1/2] net: dsa: mv88e6xxx: rename mv88e6xxx_g2_scratch_gpio_set_smi Robert Marko
2024-02-27 19:23 ` Andrew Lunn
2024-02-27 17:54 ` [PATCH net-next v2 2/2] net: dsa: mv88e6xxx: add Amethyst specific SMI GPIO function Robert Marko
2024-02-29 9: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=170919902947.26621.622513714154438592.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robimarko@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