From: Rob Herring <robh@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
"arm@kernel.org" <arm@kernel.org>
Subject: Re: [PATCH 0/3] dtc updates for 4.12
Date: Tue, 21 Mar 2017 14:36:02 -0500 [thread overview]
Message-ID: <CAL_Jsq+CBiV_px_RMaxK1d6F1Bo5JbLjX74TPV_VCygcdWs9yw@mail.gmail.com> (raw)
In-Reply-To: <1e151194-0768-7f73-cd5c-21f42a6555de@gmail.com>
On Tue, Mar 21, 2017 at 11:49 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 03/21/2017 09:19 AM, Rob Herring wrote:
>> This series syncs dtc with current mainline. The primary motivation is
>> to pull in the new checks I've worked on. This gives lots of new
>> warnings which are turned off by default.
>>
>> Arm-soc folks, I've left the PCI checks enabled as they are pretty much
>> all real errors and there aren't that many (about 1200, but that's lots
>> of duplicates). I have a patch for some of them.
>
> Out of curiosity, should we think about making dtc a git submodule and
> have some magic in scripts/update-dtc-source.sh to sync it to a desired
> commit?
I'd be fine with that though all of dtc is not imported and I don't
really want to be the first to try to add a git submodule to the
kernel. Not everyone is a fan I think.
Rob
next prev parent reply other threads:[~2017-03-21 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:19 [PATCH 0/3] dtc updates for 4.12 Rob Herring
2017-03-21 16:19 ` [PATCH 1/3] scripts/dtc: automate getting dtc version and log in update script Rob Herring
2017-03-21 16:19 ` [PATCH 2/3] scripts/dtc: Update to upstream version v1.4.4-8-g756ffc4f52f6 Rob Herring
2017-03-21 16:19 ` [PATCH 3/3] dtc: update warning settings for new bus and node/property name checks Rob Herring
2017-03-21 16:49 ` [PATCH 0/3] dtc updates for 4.12 Florian Fainelli
2017-03-21 19:36 ` Rob Herring [this message]
2017-03-21 19:15 ` Olof Johansson
[not found] ` <CAOesGMiWFPERPapOLCW4iqSuFWiqesBBjGN0ny6XjzFXNfKr4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-21 19:55 ` Rob Herring
2017-03-29 21:41 ` Rob Herring
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=CAL_Jsq+CBiV_px_RMaxK1d6F1Bo5JbLjX74TPV_VCygcdWs9yw@mail.gmail.com \
--to=robh@kernel.org \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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).