From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH] libfdt: reduce the number of headers included from libfdt_env.h
Date: Thu, 17 Oct 2019 13:46:07 -0500 [thread overview]
Message-ID: <fcba8d22-008a-58b7-57ae-ef5fbc6234bc@gmail.com> (raw)
In-Reply-To: <CAL_JsqJHGcbf-p7D=MvSRiX_7CVY0Kj9bRKybhbWG=4MxaxGiw@mail.gmail.com>
On 10/17/2019 12:52, Rob Herring wrote:
> On Thu, Oct 17, 2019 at 12:25 PM Frank Rowand <frowand.list@gmail.com> wrote:
>>
>> On 10/17/2019 11:34, Rob Herring wrote:
>>> On Wed, Oct 16, 2019 at 08:01:46PM +0900, Masahiro Yamada wrote:
>>>> Hi Andrew,
>>>>
>>>> Could you pick up this to akpm tree?
>>>> https://lore.kernel.org/patchwork/patch/1089856/
>>>>
>>>> I believe this is correct, and a good clean-up.
>>>>
>>>> I pinged the DT maintainers, but they did not respond.
>>>
>>> Sorry I missed this. Things outside my normal paths fall thru the
>>> cracks.
>>>
>>> I'll apply it now.
>>>
>>> Rob
>>>
>>
>> Looks like my reply crossed with Rob's. Rob, shouldn't
>> scripts/dtc/update-dtc-source.sh make this change?
>
> No, the includes in include/linux are kernel files which wrap/replace
> the upstream ones.
>
> Rob
>
Right you are, I overlooked the "include/linux" in the file name
instead of "scripts/dtc/libfdt/".
-Frank
next prev parent reply other threads:[~2019-10-17 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 16:21 [PATCH] libfdt: reduce the number of headers included from libfdt_env.h Masahiro Yamada
2019-08-01 2:30 ` Masahiro Yamada
2019-08-19 4:36 ` Masahiro Yamada
2019-10-16 11:01 ` Masahiro Yamada
2019-10-17 16:34 ` Rob Herring
2019-10-17 17:25 ` Frank Rowand
2019-10-17 17:52 ` Rob Herring
2019-10-17 18:46 ` Frank Rowand [this message]
2019-10-17 17:23 ` Frank Rowand
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=fcba8d22-008a-58b7-57ae-ef5fbc6234bc@gmail.com \
--to=frowand.list@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=yamada.masahiro@socionext.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