linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom arm64 Device Tree fixes for 4.11
Date: Wed, 22 Mar 2017 11:03:00 -0700	[thread overview]
Message-ID: <20170322180300.27599-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20170322180300.27599-1-f.fainelli@gmail.com>

The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:

  Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)

are available in the git repository at:

  http://github.com/Broadcom/stblinux tags/arm-soc/for-4.11/devicetree-arm64-fixes

for you to fetch changes up to f0c0cb99f74c03e2407ea553f6d46eb611e262b5:

  arm64: dts: NS2: Add dma-coherent to relevant DT entries (2017-03-22 10:14:14 -0700)

----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs Device Tree fixes for 4.11,
please pull the following:

- Jon adds missing "dma-coherent" property to the Northstar 2 DTS include file
  in order to fix both performance and cache problems for: PCIe, Ethernet,
  PDC/mailbox, SATA3 and SDHCI

----------------------------------------------------------------
Jon Mason (1):
      arm64: dts: NS2: Add dma-coherent to relevant DT entries

 arch/arm64/boot/dts/broadcom/ns2.dtsi | 11 +++++++++++
 1 file changed, 11 insertions(+)

  reply	other threads:[~2017-03-22 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 18:02 [GIT PULL 1/2] Broadcom arm Device Tree fixes for 4.11 (part 2) Florian Fainelli
2017-03-22 18:03 ` Florian Fainelli [this message]
2017-03-24 16:57   ` [GIT PULL 2/2] Broadcom arm64 Device Tree fixes for 4.11 Arnd Bergmann
2017-03-24 16:51 ` [GIT PULL 1/2] Broadcom arm Device Tree fixes for 4.11 (part 2) Arnd Bergmann

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=20170322180300.27599-2-f.fainelli@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).