All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Rob Herring <robherring2@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Mark Rutland <mark.rutland@arm.com>,
	DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Devicetree updates for 4.20
Date: Sun, 28 Oct 2018 22:25:41 -0700	[thread overview]
Message-ID: <CAOesGMh=iJ-LE25ooVmoSVD7Rw9AzrJhXbP2X4+OeeUwmV5HnQ@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqJKkPiHBbJWMF5=JzxZyO+UTN0qLFLnjvd9txkUQPdznw@mail.gmail.com>

Hi Rob,

On Fri, Oct 26, 2018 at 9:07 AM Rob Herring <robherring2@gmail.com> wrote:
>
> Linus,
>
> Please pull DT updates for 4.20. A bit bigger than normal as I've been
> busy this cycle. There's a few things with dependencies and a few
> things subsystem maintainers didn't pick up, so I'm taking them thru
> my tree. The fixes from Johan didn't get into linux-next, but they've
> been waiting for some time now and they are what's left of what
> subsystem maintainers didn't pick up. There's no conflicts yet with
> your tree, but there are 2 conflicts I'm aware of. One is with the c6x
> tree and the other is in drivers/soc/qcom/apr.c. The correct
> resolutions are in linux-next.
>
[...]

>       scripts/dtc: Update to upstream version v1.4.7-14-gc86da84d30e4

This update made dtc spit out a large number of warnings on a regular
build, due to a new requirement that a SPI node is named "spi". Seems
like an arbitrary restriction, but either way can the warning please
be disabled by default until them cleaned up so we don't have a bunch
of noise in the logs?

An example ARM allmodconfig:
http://arm-soc.lixom.net/buildlogs/mainline/v4.19-9418-g9f51ae62c84a2/buildall.arm.allmodconfig.log.passed
(162 warnings).

Thanks,

-Olof

  parent reply	other threads:[~2018-10-29  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 16:06 [GIT PULL] Devicetree updates for 4.20 Rob Herring
2018-10-26 19:12 ` Linus Torvalds
2018-10-29  5:25 ` Olof Johansson [this message]
2018-10-29 12:44   ` Rob Herring
2018-10-29 14:34     ` 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='CAOesGMh=iJ-LE25ooVmoSVD7Rw9AzrJhXbP2X4+OeeUwmV5HnQ@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robherring2@gmail.com \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.