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] ARM: dts: uniphier: UniPhier DT updates for v4.14
Date: Wed, 16 Aug 2017 23:31:50 +0200	[thread overview]
Message-ID: <CAK8P3a1qY1UCVcFmmJ4Df=27xZqeEh91XZdW1udMSUNcb-ZeyA@mail.gmail.com> (raw)
In-Reply-To: <CAK7LNAQpsNrrrL2T8J1QYjA+9cmj8UO3JdTCZ7_WLGfdWC4G7w@mail.gmail.com>

On Wed, Aug 16, 2017 at 5:00 AM, Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:

> ----------------------------------------------------------------
> UniPhier ARM SoC DT updates for v4.14
>
> - complete migrating to SPDX License Identifier
> - remove support for old SoC
> - add nodes for NAND, Audio pinctrl
> - replace /include/ with #include
>
> ----------------------------------------------------------------
> Katsuhiro Suzuki (1):
>       ARM: dts: uniphier: add audio out pin-mux node
>
> Masahiro Yamada (4):
>       ARM: dts: uniphier: use SPDX-License-Identifier (2nd)
>       ARM: dts: uniphier: remove sLD3 SoC support
>       ARM: dts: uniphier use #include instead of /include/
>       ARM: dts: uniphier: add Denali NAND controller node

Pulled into next/dt, but please clarify one question:

How likely is it that there are still users of the sLD3 SoC on
mainline kernels? The commit just states that it is too hard
to maintain, but the more important question is whether anyone
cares about it breaking.

      Arnd

  reply	other threads:[~2017-08-16 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16  3:00 [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.14 Masahiro Yamada
2017-08-16 21:31 ` Arnd Bergmann [this message]
2017-08-17  7:46   ` Masahiro Yamada
  -- strict thread matches above, loose matches on Subject: below --
2017-08-28 15:23 Masahiro Yamada
2017-08-30  5:41 ` Olof Johansson

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='CAK8P3a1qY1UCVcFmmJ4Df=27xZqeEh91XZdW1udMSUNcb-ZeyA@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).