From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2)
Date: Sun, 5 Mar 2017 22:21:33 -0800 [thread overview]
Message-ID: <aa4a7b78-3cd9-66d0-953c-961cb10c9207@gmail.com> (raw)
In-Reply-To: <20170306042913.phr6ooew4mkcbss6@tarshish>
On 03/05/2017 08:29 PM, Baruch Siach wrote:
> Hi Florian, ARM SoC maintainers,
>
> On Wed, Feb 01, 2017 at 06:06:07PM -0800, Florian Fainelli wrote:
>> The following changes since commit c5a8e3add28ca4063410353acfbe6e650174e432:
>>
>> Merge tag 'bcm2835-dt-next-2017-01-17' into devicetree/next (2017-01-18 17:20:32 -0800)
>>
>> are available in the git repository at:
>>
>> http://github.com/Broadcom/stblinux tags/arm-soc/for-4.11/devicetree-part2
>>
>> for you to fetch changes up to c206e53d4c672ec83a4fc4d70eeac22d4b4ca80d:
>>
>> Merge tag 'bcm2835-dt-next-2017-01-31' into devicetree/next (2017-02-01 17:37:59 -0800)
>>
>> ----------------------------------------------------------------
>> This pull request contains the second round of Device Tree updates for Broadcom
>> ARM-based SoCs for 4.11, please pull the following:
>>
>> - Rafal adds support for two new Linksys routers: Linksys EA9200 (BCM4709) and
>> Linksys EA6300 V1 (BCM4708)
>>
>> - Dhanajay adds supports for the USB Device Tree nodes to the Northstar Plus
>> SoC
>>
>> - Baruch makes several fixes to the uart0 pinctrl node names, fixes the i2c0 pins
>> and the uart0/uart1 pins as well. Finally, he adds proper indexes to the ethernet
>> aliases
>>
>> - Eric merges a topic branch from the clk tree to incorporate several DSI0/1 pixel
>> clock requirements and he finally proceeds with adding proper DSI modules nodes
>> and clocks to the BCM2835 Device Tree
>>
>> Please note that because of the "clk" topic branch merged by Eric, we end-up with
>> pulling in v4.10-rc2 which is responsible for the funny diff here.
>
> What happened to this pull request? v4.11-rc1 is out now.
It was submitted too late, and therefore got postponed, so everything
that's in there should show up for 4.12 now once Eric re-submits the
BCM283x pull request in a few days.
--
Florian
next prev parent reply other threads:[~2017-03-06 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 2:06 [GIT PULL 1/2] Broadcom dts changes for 4.11 (part 2) Florian Fainelli
2017-02-07 14:49 ` Arnd Bergmann
2017-02-07 20:59 ` Florian Fainelli
2017-02-07 21:12 ` Arnd Bergmann
2017-02-07 23:52 ` Eric Anholt
2017-02-08 9:01 ` Arnd Bergmann
2017-02-09 19:16 ` Florian Fainelli
2017-02-07 21:05 ` Eric Anholt
2017-03-06 4:29 ` Baruch Siach
2017-03-06 6:21 ` Florian Fainelli [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-02 2:04 Florian Fainelli
2017-02-02 2:06 ` 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=aa4a7b78-3cd9-66d0-953c-961cb10c9207@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).