From: patchwork-bot+netdevbpf@kernel.org
To: Rob Herring <robh@kernel.org>
Cc: jaswinder.singh@linaro.org, ilias.apalodimas@linaro.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, krzysztof.kozlowski+dt@linaro.org,
ardb@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: Convert Socionext NetSec Ethernet to DT schema
Date: Mon, 12 Dec 2022 21:11:12 +0000 [thread overview]
Message-ID: <167087947263.28989.14967575841484892448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209171553.3350583-1-robh@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Dec 2022 11:15:52 -0600 you wrote:
> Convert the Socionext NetSec Ethernet binding to DT schema format.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> .../net/socionext,synquacer-netsec.yaml | 73 +++++++++++++++++++
> .../bindings/net/socionext-netsec.txt | 56 --------------
> MAINTAINERS | 2 +-
> 3 files changed, 74 insertions(+), 57 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/socionext,synquacer-netsec.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/socionext-netsec.txt
Here is the summary with links:
- dt-bindings: net: Convert Socionext NetSec Ethernet to DT schema
https://git.kernel.org/bpf/bpf-next/c/15eb16217621
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-12-12 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 17:15 [PATCH] dt-bindings: net: Convert Socionext NetSec Ethernet to DT schema Rob Herring
2022-12-09 19:40 ` Jassi Brar
2022-12-12 21:11 ` 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=167087947263.28989.14967575841484892448.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--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@kernel.org \
/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).