From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
"open list\:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH v3 0/8] ARM: dts: Switch to new DSA binding
Date: Thu, 19 Jan 2017 23:48:33 +0100 [thread overview]
Message-ID: <878tq67jjy.fsf@free-electrons.com> (raw)
In-Reply-To: <633afd2c-75e4-adeb-f3a0-b59b5f47f1a7@gmail.com> (Florian Fainelli's message of "Thu, 19 Jan 2017 14:26:21 -0800")
Hi Florian,
On jeu., janv. 19 2017, Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 01/17/2017 10:22 AM, Florian Fainelli wrote:
>> Hi all,
>>
>> This patch series converts the in-tree users to utilize the new (relatively)
>> DSA binding that was introduced with commit 8c5ad1d6179d ("net: dsa: Document
>> new binding"). The legacy binding node is kept included, but is marked
>> disabled.
>>
>> Changes in v3:
>>
>> - collected tags from Andrew and Russell
>> - added missing change to arch/arm/boot/dts/kirkwood-rd88f6281-a.dts
>>
>> Changes in v2:
>>
>> - patch 1: Use an hexadecimal reg property
>> - patch 2: fixed the subject
>> - patch 3: s/okay/disabled/ for the legacy DSA node
>> - patches 7/8: fixed a stray whitespace
>>
>> In about 2-3 releases we may consider removing the old DSA binding entirely
>> from the kernel.
>
> Gregory, all patches have been reviewed/tested now, can you take this
> for an upcoming 4.11 pull request? Thanks!
All the series applied on mvebu/dt
Thanks,
Gregory
> --
> Florian
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-01-19 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 18:22 Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 1/8] ARM: dts: armada-370-rd: Utilize " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 2/8] ARM: dts: armada-385-linksys: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 3/8] ARM: dts: armada-388-clearfog: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 4/8] ARM: dts: armada-xp-linksys-mamba: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 5/8] ARM: dts: kirkwood-dir665: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 6/8] ARM: dts: kirkwood-linksys-viper: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 7/8] ARM: dts: kirkwood-mv88f6281gtw-ge: " Florian Fainelli
2017-01-17 18:22 ` [PATCH v3 8/8] ARM: dts: kirkwood-rd88f6281: " Florian Fainelli
2017-01-18 12:57 ` Andrew Lunn
2017-01-19 22:26 ` [PATCH v3 0/8] ARM: dts: Switch to " Florian Fainelli
2017-01-19 22:48 ` Gregory CLEMENT [this message]
2017-01-19 22:49 ` Florian Fainelli
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=878tq67jjy.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=vivien.didelot@savoirfairelinux.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
Powered by JetHome