From: "Rafał Miłecki" <rafal@milecki.pl>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
"Rob Herring" <robh+dt@kernel.org>,
"Andrew Lunn" <andrew@lunn.ch>,
"Vivien Didelot" <vivien.didelot@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Vladimir Oltean" <olteanv@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH V2 net-next 1/3] dt-bindings: net: convert Broadcom Starfighter 2 binding to the json-schema
Date: Sun, 10 Jan 2021 11:10:08 +0100 [thread overview]
Message-ID: <00fffaaaaa4b1120a6c71bca82172296@milecki.pl> (raw)
In-Reply-To: <20210109191957.1ef47d28@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On 2021-01-10 04:19, Jakub Kicinski wrote:
> On Wed, 6 Jan 2021 22:32:00 +0100 Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@milecki.pl>
>>
>> This helps validating DTS files. Only the current (not deprecated one)
>> binding was converted.
>>
>> Minor changes:
>> 1. Dropped dsa/dsa.txt references
>> 2. Updated node name to match dsa.yaml requirement
>> 3. Fixed 2 typos in examples
>>
>> The new binding was validated using the dt_binding_check.
>>
>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>
> Applied, I trust you'll follow up promptly if Rob finds anything wrong
> with the DT parts :)
Promise! :)
next prev parent reply other threads:[~2021-01-10 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 21:32 [PATCH V2 net-next 1/3] dt-bindings: net: convert Broadcom Starfighter 2 binding to the json-schema Rafał Miłecki
2021-01-06 21:32 ` [PATCH V2 net-next 2/3] dt-bindings: net: dsa: sf2: add BCM4908 switch binding Rafał Miłecki
2021-01-06 21:32 ` [PATCH V2 net-next 3/3] net: dsa: bcm_sf2: support BCM4908's integrated switch Rafał Miłecki
2021-01-10 3:19 ` [PATCH V2 net-next 1/3] dt-bindings: net: convert Broadcom Starfighter 2 binding to the json-schema Jakub Kicinski
2021-01-10 10:10 ` Rafał Miłecki [this message]
2021-01-10 3:30 ` patchwork-bot+netdevbpf
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=00fffaaaaa4b1120a6c71bca82172296@milecki.pl \
--to=rafal@milecki.pl \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=zajec5@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