linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/1] Broadcom devicetree fixes for 4.14
Date: Thu, 19 Oct 2017 17:35:36 +0200	[thread overview]
Message-ID: <CAK8P3a3-XhQtw+BsZXTC_PYpDxEeqYhkUhpjemLoiGPL8hgTAQ@mail.gmail.com> (raw)
In-Reply-To: <20171006222014.2704-1-f.fainelli@gmail.com>

On Sat, Oct 7, 2017 at 12:20 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoC Device Tree fixes for 4.14,
> please pull the following:
>
> - Loic fixes the console path on the Raspberry Pi 3 which was not correctly set
>   and would cause all sorts of confusion between the Bluetooth controller and the
>   kernel console

Sorry for the delay. I've merged it into fixes now to make things work for you,
though it still seems that there is something wrong with the patch: you now
have the 'aliases' node in the bcm283x.dtsi, which doesn't seem appropriate.
There might be different board based on the same chip that don't all expose
the same uarts at the same physical connectors, and you might have a .dts
file that overrides those aliases, which gets really messy.

Please put the aliases list into each .dts file for this platform and make
sure you list them with the right numbers.

     Arnd

      reply	other threads:[~2017-10-19 15:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 22:20 [GIT PULL 1/1] Broadcom devicetree fixes for 4.14 Florian Fainelli
2017-10-19 15:35 ` Arnd Bergmann [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=CAK8P3a3-XhQtw+BsZXTC_PYpDxEeqYhkUhpjemLoiGPL8hgTAQ@mail.gmail.com \
    --to=arnd@arndb.de \
    --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).