From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scripts/dtc: dtx_diff - add info to error message
Date: Fri, 12 Feb 2016 09:37:57 -0800 [thread overview]
Message-ID: <56BE1875.5010307@gmail.com> (raw)
In-Reply-To: <CAL_JsqL0CpbcACqNjo1u7KYUz_rnKVWj8ZjKuyE2mefNw=Li4A@mail.gmail.com>
On 2/11/2016 5:41 PM, Rob Herring wrote:
> On Thu, Feb 11, 2016 at 6:50 PM, Frank Rowand <frowand.list@gmail.com> wrote:
>> On 2/2/2016 11:02 AM, Frank Rowand wrote:
>>> From: Frank Rowand <frank.rowand@sonymobile.com>
>>>
>>> If kernel config options are not properly set, "make scripts" will not
>>> compile dtc. Update the unable to find dtc error message to check
>>> the kernel config and give better advice on how to create dtc.
>>>
>>> Reword another error message to increase clarity.
>>>
>>> Signed-off-by: Frank Rowand <frank.rowand@sonymobile.com>
>>
>> < snip >
>>
>> Ping, no reply on original email.
>
> No comment, no reply. I only reply with "applied" when I actually
> apply stuff which tends to be at least several weeks. Otherwise, I
> might tell you applied and then miss it. :)
>
> Anyway, now applied.
>
>> In the thread about the of ir msi-map patch you mentioned that you have nothing
>> else queued for 4.5. Is dtx_diff (and hopefully this patch) queued up for 4.6?
>> If so, could they instead go into 4.5 since they are support tools, and do not
>> directly impact the kernel?
>
> It's not a fix either though, so no, it's queued for 4.6 and has been
> since -rc1.
>
> Rob
>
Ok, thanks!
-Frank
prev parent reply other threads:[~2016-02-12 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 19:02 [PATCH] scripts/dtc: dtx_diff - add info to error message Frank Rowand
2016-02-12 0:50 ` Frank Rowand
2016-02-12 1:41 ` Rob Herring
2016-02-12 17:37 ` Frank Rowand [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=56BE1875.5010307@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).