From: Rob Herring <robh+dt@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Elliot Berman <eberman@codeaurora.org>,
Michal Marek <michal.lkml@markovi.net>,
Frank Rowand <frowand.list@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Steve Muckle <smuckle@google.com>,
Trilok Soni <tsoni@codeaurora.org>
Subject: Re: [PATCH] kbuild: Add dtc flag test
Date: Mon, 24 May 2021 09:21:55 -0500 [thread overview]
Message-ID: <CAL_JsqJNkEmw_94aP95o+hMdA_nJLc+wkEMcOzYdzeYzYUbOVg@mail.gmail.com> (raw)
In-Reply-To: <CAF2Aj3j7S3YXM-eFxWR7vOUMmN=gDEenmNLZP31iDTkBWG2PgQ@mail.gmail.com>
On Mon, May 24, 2021 at 6:40 AM Lee Jones <lee.jones@linaro.org> wrote:
>
> On Thu, 6 Aug 2020 at 03:22, Masahiro Yamada <masahiroy@kernel.org> wrote:
>>
>> On Thu, Aug 6, 2020 at 2:59 AM Elliot Berman <eberman@codeaurora.org> wrote:
>> >
>> > Host dtc may not support the same flags as kernel's copy of dtc. Test
>> > if dtc supports each flag when the dtc comes from host.
>> >
>> > Signed-off-by: Elliot Berman <eberman@codeaurora.org>
>>
>>
>> I think this supports only the newer external DTC,
>> but not older ones.
>>
>> This feature is intended to test the upstream DTC
>> before resyncing in-kernel scripts/dtc/.
>
>
> Was there ever a follow-up to this?
As Masahiro said, using an older dtc is not a usecase we care about.
Rob
prev parent reply other threads:[~2021-05-24 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 17:58 [PATCH] kbuild: Add dtc flag test Elliot Berman
2020-08-06 2:21 ` Masahiro Yamada
[not found] ` <CAF2Aj3j7S3YXM-eFxWR7vOUMmN=gDEenmNLZP31iDTkBWG2PgQ@mail.gmail.com>
2021-05-24 14:21 ` Rob Herring [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=CAL_JsqJNkEmw_94aP95o+hMdA_nJLc+wkEMcOzYdzeYzYUbOVg@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eberman@codeaurora.org \
--cc=frowand.list@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=smuckle@google.com \
--cc=tsoni@codeaurora.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).