From: patchwork-bot+netdevbpf@kernel.org
To: Pandey@ci.codeaurora.org, Radhey Shyam <radhey.shyam.pandey@amd.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, harini.katakam@amd.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, git@amd.com
Subject: Re: [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx emaclite driver binding
Date: Wed, 15 Jun 2022 08:30:13 +0000 [thread overview]
Message-ID: <165528181375.16320.16353044588211056289.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1654793615-21290-1-git-send-email-radhey.shyam.pandey@amd.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 9 Jun 2022 22:23:35 +0530 you wrote:
> Add basic description for the xilinx emaclite driver DT bindings.
>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
> ---
> Changes since v1:
> - Move ethernet-controller.yaml reference after maintainers.
> - Drop interrupt second cell in example node.
> - Set local-mac-address to all 0s in example node.
> - Put the reg after compatible in DTS code.
>
> [...]
Here is the summary with links:
- [v2,net-next] dt-bindings: net: xilinx: document xilinx emaclite driver binding
https://git.kernel.org/netdev/net-next/c/3a51e969fa90
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-06-15 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 16:53 [PATCH v2 net-next] dt-bindings: net: xilinx: document xilinx emaclite driver binding Radhey Shyam Pandey
2022-06-14 9:09 ` Paolo Abeni
2022-06-14 21:09 ` Pandey, Radhey Shyam
2022-06-14 22:48 ` Krzysztof Kozlowski
2022-06-14 22:57 ` Krzysztof Kozlowski
2022-06-15 1:54 ` Jakub Kicinski
2022-06-16 17:46 ` Rob Herring
2022-06-15 8: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=165528181375.16320.16353044588211056289.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Pandey@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.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=radhey.shyam.pandey@amd.com \
--cc=robh+dt@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