From: Frank Rowand <frowand.list@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Michal Marek <mmarek@suse.cz>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: [Patch v3 1/3] dt: OF_UNITTEST make dependency broken, framework fixes
Date: Fri, 13 Mar 2015 12:18:14 -0700 [thread overview]
Message-ID: <550337F6.70404@gmail.com> (raw)
In-Reply-To: <CAL_JsqLbXJFT4+bnyksHmE9TWJbHuHpujiJOc2MOajO5Xem_+g@mail.gmail.com>
On 3/13/2015 6:13 AM, Rob Herring wrote:
> On Thu, Mar 12, 2015 at 8:15 AM, Frank Rowand <frowand.list@gmail.com> wrote:
>> From: Frank Rowand <frank.rowand@sonymobile.com>
>>
>> This 3 patch series is not bisectable. If CONFIG_OF_UNITTEST=y then the kernel
>> will not build with just patch 1 or just patches 1 and 2 applied.
>
> If you did 2 patches with the move first, wouldn't that make it
> bisectable. However, I'd rather avoid the move.
Yes, I did not like the move either. Fortunately you gave me the cluebat I needed
to avoid the move.
>
>> If CONFIG_OF_UNITTEST=y then a kernel image make will always cause .version to
>> be incremented, even if there are not source changes. This is caused by
>> a lack of dependency tracking and checking for
>> drivers/of/unittest-data/testcases.dtb.o. Fixing the problem was made more
>> complicated by the fact that testcases.dtb.o was linked into ../of_unittest.o.
>
> Couldn't we change that to be 2 modules.
Thanks, that was just the hint I needed to realize that of_unittest.o was
just an artifact of the problem I was trying to solve. I will send a new
patch that removes the of_unittest.o cruft and does not need to move unittest.c
>
>> Patch 1 modifies makefiles to move of_unittest.c into unittest-data/ and
>> creates missing dependency tracking for testcases.dtb.o.
>>
>> Patch 2 will move of_unittest.c into unittest-data/
>>
>> Patch 3 will fix an of_unittest.c include path to account for the move.
>
> This should all be in an intro email, not patch #1.
prev parent reply other threads:[~2015-03-13 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 13:15 [Patch v3 1/3] dt: OF_UNITTEST make dependency broken, framework fixes Frank Rowand
[not found] ` <5501918D.2020000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-12 13:17 ` [Patch v3 2/3] dt: OF_UNITTEST make dependency broken, move unittest.c Frank Rowand
2015-03-12 13:18 ` [Patch v3 3/3] dt: OF_UNITTEST make dependency broken, fix unittest.c after move Frank Rowand
2015-03-13 13:13 ` [Patch v3 1/3] dt: OF_UNITTEST make dependency broken, framework fixes Rob Herring
2015-03-13 19:18 ` 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=550337F6.70404@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.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).