public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Cc: devicetree@vger.kernel.org, arnd@arndb.de, olof@lixom.net,
	arinc.unal@arinc9.com, f.fainelli@gmail.com,
	sfr@canb.auug.org.au, linus.walleij@linaro.org, andrew@lunn.ch,
	vivien.didelot@gmail.com, olteanv@gmail.com, davem@davemloft.net,
	kuba@kernel.org, robh+dt@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: net: dsa: realtek: convert to YAML schema, add MDIO
Date: Fri, 11 Feb 2022 12:00:13 +0000	[thread overview]
Message-ID: <164458081381.17283.252539054046225452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209184116.18094-1-luizluca@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed,  9 Feb 2022 15:41:16 -0300 you wrote:
> Schema changes:
> 
> - support for mdio-connected switches (mdio driver), recognized by
>   checking the presence of property "reg"
> - new compatible strings for rtl8367s and rtl8367rb
> - "interrupt-controller" was not added as a required property. It might
>   still work polling the ports when missing.
> 
> [...]

Here is the summary with links:
  - [v2] dt-bindings: net: dsa: realtek: convert to YAML schema, add MDIO
    https://git.kernel.org/netdev/net-next/c/429c83c78ab2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-02-11 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 18:41 [PATCH v2] dt-bindings: net: dsa: realtek: convert to YAML schema, add MDIO Luiz Angelo Daros de Luca
2022-02-11  1:16 ` Linus Walleij
2022-02-11 12:00 ` 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=164458081381.17283.252539054046225452.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=arinc.unal@arinc9.com \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luizluca@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=olteanv@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vivien.didelot@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