From: patchwork-bot+netdevbpf@kernel.org
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robimarko@gmail.com, daniel@makrotopia.org,
rmk+kernel@armlinux.org.uk, frut3k7@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [net-next PATCH v3 1/2] net: phy: aquantia: move priv and hw stat to header
Date: Wed, 05 Jun 2024 09:30:29 +0000 [thread overview]
Message-ID: <171757982994.5772.18334468085942264665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240531233505.24903-1-ansuelsmth@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 1 Jun 2024 01:35:02 +0200 you wrote:
> In preparation for LEDs support, move priv and hw stat to header to
> reference priv struct also in other .c outside aquantia.main
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> ---
> Changes v2:
> - Out of RFC
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: phy: aquantia: move priv and hw stat to header
https://git.kernel.org/netdev/net-next/c/c11d5dbbe73f
- [net-next,v3,2/2] net: phy: aquantia: add support for PHY LEDs
https://git.kernel.org/netdev/net-next/c/61578f679378
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-06-05 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 23:35 [net-next PATCH v3 1/2] net: phy: aquantia: move priv and hw stat to header Christian Marangi
2024-05-31 23:35 ` [net-next PATCH v3 2/2] net: phy: aquantia: add support for PHY LEDs Christian Marangi
2024-06-02 13:56 ` [net-next PATCH v3 1/2] net: phy: aquantia: move priv and hw stat to header Andrew Lunn
2024-06-05 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=171757982994.5772.18334468085942264665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frut3k7@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--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