From: patchwork-bot+netdevbpf@kernel.org
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andrew@lunn.ch,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema
Date: Wed, 11 May 2022 02:20:12 +0000 [thread overview]
Message-ID: <165223561236.21834.15484862812864073697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220505210621.3637268-1-chris.packham@alliedtelesis.co.nz>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 6 May 2022 09:06:20 +1200 you wrote:
> Convert the marvell,orion-mdio binding to JSON schema.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
>
> Notes:
> This does throw up the following dtbs_check warnings for turris-mox:
>
> [...]
Here is the summary with links:
- [v2] dt-bindings: net: orion-mdio: Convert to JSON schema
https://git.kernel.org/netdev/net-next/c/0781434af811
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-05-11 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 21:06 [PATCH v2] dt-bindings: net: orion-mdio: Convert to JSON schema Chris Packham
2022-05-10 0:28 ` Jakub Kicinski
2022-05-10 0:41 ` Andrew Lunn
2022-05-10 0:43 ` Jakub Kicinski
2022-05-16 18:14 ` Rob Herring
2022-05-10 0:47 ` Chris Packham
2022-05-10 23:12 ` Andrew Lunn
2022-05-11 2:20 ` patchwork-bot+netdevbpf [this message]
2022-05-16 18:16 ` Rob Herring
2022-05-16 22:18 ` Chris Packham
2022-05-16 22:27 ` Chris Packham
2022-05-18 16:18 ` Rob Herring
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=165223561236.21834.15484862812864073697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--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 \
/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).