From: patchwork-bot+netdevbpf@kernel.org
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Jose.Abreu@synopsys.com, andrew@lunn.ch, pabeni@redhat.com,
mengyuanlou@net-swift.com, alexandre.torgue@foss.st.com,
netdev@vger.kernel.org, openbmc@lists.ozlabs.org,
tmaimon77@gmail.com, linux@armlinux.org.uk,
jiawenwu@trustnetic.com, maxime.chevallier@bootlin.com,
edumazet@google.com, joabreu@synopsys.com, kuba@kernel.org,
olteanv@gmail.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, hkallweit1@gmail.com
Subject: Re: [PATCH net-next v2 0/4] net: pcs: xpcs: Cleanups before adding MMIO dev support
Date: Mon, 26 Feb 2024 13:10:30 +0000 [thread overview]
Message-ID: <170895303039.847.5849181262053799577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240222175843.26919-1-fancer.lancer@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 22 Feb 2024 20:58:19 +0300 you wrote:
> As stated in the subject this series is a short prequel before submitting
> the main patches adding the memory-mapped DW XPCS support to the DW XPCS
> and DW *MAC (STMMAC) drivers. Originally it was a part of the bigger
> patchset (see the changelog v2 link below) but was detached to a
> preparation set to shrink down the main series thus simplifying it'
> review.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] net: pcs: xpcs: Drop sentinel entry from 2500basex ifaces list
https://git.kernel.org/netdev/net-next/c/0ffc3292c02b
- [net-next,v2,2/4] net: pcs: xpcs: Drop redundant workqueue.h include directive
https://git.kernel.org/netdev/net-next/c/e26802ebd295
- [net-next,v2,3/4] net: pcs: xpcs: Return EINVAL in the internal methods
https://git.kernel.org/netdev/net-next/c/f5151005d379
- [net-next,v2,4/4] net: pcs: xpcs: Explicitly return error on caps validation
https://git.kernel.org/netdev/net-next/c/361dd531a11b
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-26 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:58 [PATCH net-next v2 0/4] net: pcs: xpcs: Cleanups before adding MMIO dev support Serge Semin
2024-02-22 17:58 ` [PATCH net-next v2 1/4] net: pcs: xpcs: Drop sentinel entry from 2500basex ifaces list Serge Semin
2024-02-22 17:58 ` [PATCH net-next v2 2/4] net: pcs: xpcs: Drop redundant workqueue.h include directive Serge Semin
2024-02-22 17:58 ` [PATCH net-next v2 3/4] net: pcs: xpcs: Return EINVAL in the internal methods Serge Semin
2024-02-22 17:58 ` [PATCH net-next v2 4/4] net: pcs: xpcs: Explicitly return error on caps validation Serge Semin
2024-02-23 9:56 ` Maxime Chevallier
2024-02-26 13: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=170895303039.847.5849181262053799577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jiawenwu@trustnetic.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pabeni@redhat.com \
--cc=tmaimon77@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).