From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Add FEC support on s32v234 platform
Date: Tue, 20 Sep 2022 01:10:20 +0000 [thread overview]
Message-ID: <166363622090.23429.15584862562185231209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220907095649.3101484-1-wei.fang@nxp.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Sep 2022 17:56:47 +0800 you wrote:
> From: Wei Fang <wei.fang@nxp.com>
>
> This series patches are to add FEC support on s32v234 platfom.
> 1. Add compatible string and quirks for fsl,s32v234
> 2. Update Kconfig to also check for ARCH_S32.
>
> Wei Fang (2):
> dt-bindings: net: fec: add fsl,s32v234-fec to compatible property
> net: fec: Add initial s32v234 support
>
> [...]
Here is the summary with links:
- [net-next,1/2] dt-bindings: net: fec: add fsl,s32v234-fec to compatible property
https://git.kernel.org/netdev/net-next/c/00f5303c17ee
- [net-next,2/2] net: fec: Add initial s32v234 support
https://git.kernel.org/netdev/net-next/c/167d5fe0f6c9
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:[~2022-09-20 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:56 [PATCH net-next 0/2] Add FEC support on s32v234 platform wei.fang
2022-09-07 9:56 ` [PATCH net-next 1/2] dt-bindings: net: fec: add fsl,s32v234-fec to compatible property wei.fang
2022-09-08 12:10 ` Krzysztof Kozlowski
2022-09-07 9:56 ` [PATCH net-next 2/2] net: fec: Add initial s32v234 support wei.fang
2022-09-14 1:26 ` Wei Fang
2022-09-20 1: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=166363622090.23429.15584862562185231209.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=wei.fang@nxp.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 NNTP newsgroup(s).