From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] kern-tools: unify meta directory detection
Date: Mon, 27 Apr 2015 09:51:16 -0400 [thread overview]
Message-ID: <553E3ED4.8010609@windriver.com> (raw)
In-Reply-To: <1430126328.13022.93.camel@linuxfoundation.org>
On 2015-04-27 05:18 AM, Richard Purdie wrote:
> On Fri, 2015-04-24 at 12:13 -0400, Bruce Ashfield wrote:
>> It is possible that recipe specific tasks, or build processes drop
>> files into the kernel source directory. These files can cause problems
>> with the meta data detection in the kern-tools.
>>
>> With this change, we have a single unified meta data detection routine,
>> that logs the result in a new file ".metadir", which subsequent scripts
>> can find, and use, thereby avoid repeating the same check many times.
>>
>> We also enhance the check to look for a sentinel file in a proper meta
>> directory, to avoid false positives when an unexpected kernel process
>> leaves an uncommitted directory in the kernel dir.
>>
>> [YOCTO: #7441]
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>> meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> index a1ec198fde7f..e83f195a5393 100644
>> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
>>
>> DEPENDS = "git-native"
>>
>> -SRCREV = "83e5493ea46067152609008ade131971eaebbb27"
>> +SRCREV = "79bc82453c26d426d3d8fd05d5da37cf5fc4068c"
>> PR = "r12"
>> PV = "0.2+git${SRCPV}"
>
> There is no such revision in the repo? The test builds all failed...
what ? I made that change ages ago .. I wonder if I squirreled
it away on a branch.
I should just remember to never send changes on Friday.
Fixed now.
Bruce
>
> Cheers,
>
> Richard
>
>
>
next prev parent reply other threads:[~2015-04-27 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 16:13 [PATCH 0/2] kernel: 3.19 updates and tools tweak Bruce Ashfield
2015-04-24 16:13 ` [PATCH 1/2] kern-tools: unify meta directory detection Bruce Ashfield
2015-04-27 9:18 ` Richard Purdie
2015-04-27 13:51 ` Bruce Ashfield [this message]
2015-04-24 16:13 ` [PATCH 2/2] linux-yocto/3.19: configuration updates and stable integration Bruce Ashfield
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=553E3ED4.8010609@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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