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, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH 0/2] net: phy: at803x: additional cleanup for qca808x
Date: Fri, 15 Dec 2023 10:50:25 +0000 [thread overview]
Message-ID: <170263742503.9428.5612921496608996554.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231214004432.16702-1-ansuelsmth@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 14 Dec 2023 01:44:30 +0100 you wrote:
> This small series is a preparation for the big code split. While the
> qca808x code is waiting to be reviwed and merged, we can further cleanup
> and generalize shared functions between at803x and qca808x.
>
> With these last 2 patch everything is ready to move the driver to a
> dedicated directory and split the code by creating a library module
> for the few shared functions between the 2 driver.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: phy: at803x: move specific qca808x config_aneg to dedicated function
https://git.kernel.org/netdev/net-next/c/8e732f1c6f2d
- [net-next,2/2] net: phy: at803x: make read specific status function more generic
https://git.kernel.org/netdev/net-next/c/38eb804e8458
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:[~2023-12-15 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 0:44 [net-next PATCH 0/2] net: phy: at803x: additional cleanup for qca808x Christian Marangi
2023-12-14 0:44 ` [net-next PATCH 1/2] net: phy: at803x: move specific qca808x config_aneg to dedicated function Christian Marangi
2023-12-14 0:44 ` [net-next PATCH 2/2] net: phy: at803x: make read specific status function more generic Christian Marangi
2023-12-15 10:50 ` 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=170263742503.9428.5612921496608996554.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 \
/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.