From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Brian Hutchinson <b.hutchman@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing
Date: Tue, 19 May 2015 12:31:47 -0400 [thread overview]
Message-ID: <555B6573.5030002@windriver.com> (raw)
In-Reply-To: <CADkTA4Px0rhNzfPsjcNN5Bq4sKZujkPDwnJfxq5dsKRc7=G0Aw@mail.gmail.com>
On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>>
>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>
>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I can confirm this same problem is happening to me. I just updated
>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>> fail
>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We still have a race condition in the 1.8 branch for the population
>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>
>>>>>>>>> If modules start building, they'll race against the population of the
>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>
>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>> fido yet.
>>>>>>>>>
>>>>>>>>> Bruce
>>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>> condition fixes but it wasn't obvious which one I may need. Is it
>>>>>>>> this one:
>>>>>>>
>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>
>>>>>>>
>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>
>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>> I was thinking of.
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>>> Did
>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>
>>>>>> --
>>>>>> Denys
>>>>>
>>>>> Hi Denys,
>>>>>
>>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>> Update. Not sure if I did this right but this is what I did. I added
>>>> master as a remote and cherry picked
>>>> 02d0a003d603266114512160b209876199241e98. Next I just went for it and
>>>> tried to bitbake my image again and got the same result as before.
>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>> image again and still got the same result.
>>>>
>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>> master and see if I get the same thing again. I'll leave this broken
>>>> build alone for a while in case someone wants me to try something with
>>>> it to fix it.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Yet another update ... I did a fresh checkout of master and tried to
>>> build and had the same kernelabiversion error:
>>>
>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>> now#######################
>>> | ETA:
>>> 00:00:28
>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>> now########################################
>>>
>>> | ETA: 00:00:26
>>> Parsing recipes: 100%
>>> |##############################################################################################################################################################################|
>>> Time: 00:01:02
>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>> targets, 182 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>> NOTE: multiple providers are available for u-boot (u-boot,
>>> u-boot-glsdk, u-boot-ti-staging)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>
>>> Build Configuration:
>>> BB_VERSION = "1.27.0"
>>> BUILD_SYS = "x86_64-linux"
>>> NATIVELSBSTRING = "Debian-7.8"
>>> TARGET_SYS = "arm-poky-linux-gnueabi"
>>> MACHINE = "am180x-evm"
>>> DISTRO = "poky"
>>> DISTRO_VERSION = "1.8+snapshot-20150515"
>>> TUNE_FEATURES = "arm armv5 thumb dsp"
>>> TARGET_FPU = "soft"
>>> meta
>>> meta-yocto
>>> meta-yocto-bsp = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>> meta-ti = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>> meta-oe
>>> meta-python
>>> meta-networking
>>> meta-webserver = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>> RDEPENDS [file-rdeps]
>>> ERROR: No kernel-abiversion file found
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> ERROR: Function failed: do_rootfs
>>> ERROR: Logfile of failure stored in:
>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>> rerun and 1 failed.
>>> Waiting for 0 running tasks to finish:
>>>
>>> Summary: 1 task failed:
>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs
>>> Summary: There were 4 WARNING messages shown.
>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>> More info for those that care ...
>>
>> The end of the error log file has:
>> DEBUG: Executing python function write_image_manifest
>> DEBUG: Python function write_image_manifest finished
>> NOTE: Executing: ldconfig
>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>> new -v
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> DEBUG: Python function do_rootfs finished
>> ERROR: Function failed: do_rootfs
>>
>> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>>
>
> Interesting. Looks like we have some sort of bad dependency. I'm poking around
> to see if I can reproduce this locally.
Brian,
I'm trying to wrap my head around this. Which kernel did you say
was building in your configuration ? Was it really linux-dummy, or
is there a bootable kernel in play ?
Looking at the dependencies, I can see how the depmodwrapper requires
that a kernel be built and the abiversion file created. But in the
case of linux-dummy, there's no header files to use and generate the
abiversion, so it won't be available for depmod.
Which takes me back to one of my original questions, why is depmod
running if the kernel isn't being built as part of this image .. and
that leads me to think I'm missing some important information.
Bruce
>
> Bruce
>
>> Regards,
>>
>> Brian
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Brian Hutchinson <b.hutchman@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [yocto] Migration from 1.7.1 to 1.8 - kernel-abiversion missing
Date: Tue, 19 May 2015 12:31:47 -0400 [thread overview]
Message-ID: <555B6573.5030002@windriver.com> (raw)
In-Reply-To: <CADkTA4Px0rhNzfPsjcNN5Bq4sKZujkPDwnJfxq5dsKRc7=G0Aw@mail.gmail.com>
On 2015-05-19 07:39 AM, Bruce Ashfield wrote:
> On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>> On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>> On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>>>>>
>>>>> On May 14, 2015 6:08 PM, "Denys Dmytriyenko" <denis@denix.org> wrote:
>>>>>>
>>>>>> On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote:
>>>>>>> On 2015-05-12 10:20 AM, Brian Hutchinson wrote:
>>>>>>>> On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield
>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>> On 2015-05-11 02:10 PM, Brian Hutchinson wrote:
>>>>>>>>>>
>>>>>>>>>> On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield
>>>>>>>>>> <bruce.ashfield@windriver.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>> It is plausible. But in theory, linux-dummy should still provide
>>>>>>>>>>> what you need (but since it doesn't build anything, there is
>>>>>>>>>>> no abi .. and no modules can be built against it) .. so the
>>>>>>>>>>> error isn't graceful.
>>>>>>>>>>>
>>>>>>>>>>> Bruce
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I can confirm this same problem is happening to me. I just updated
>>>>>>>>>> one of my builds from 1.7 to 1.8 and am also getting my rootfs to
>>>>>>>>>> fail
>>>>>>>>>> due to no abi kernel version:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We still have a race condition in the 1.8 branch for the population
>>>>>>>>> of the build-artifacts directory.
>>>>>>>>>
>>>>>>>>> If modules start building, they'll race against the population of the
>>>>>>>>> abiversion, and you may see that message.
>>>>>>>>>
>>>>>>>>> There's a proposed patch for master, but I don't think it is in
>>>>>>>>> fido yet.
>>>>>>>>>
>>>>>>>>> Bruce
>>>>>>>>
>>>>>>>> Hi Bruce,
>>>>>>>>
>>>>>>>> I did some searches and looks like there are a number of 'race'
>>>>>>>> condition fixes but it wasn't obvious which one I may need. Is it
>>>>>>>> this one:
>>>>>>>
>>>>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98
>>>>>>>>
>>>>>>>
>>>>>>> That's the one that should make sure that the shared workdir
>>>>>>> (Which has the abiversion) is in place before building any modules.
>>>>>>>
>>>>>>> I can't say that it is exactly your issue, but it is the change
>>>>>>> I was thinking of.
>>>>>>
>>>>>> Brian,
>>>>>>
>>>>>> Were you able to try the above mentioned commit against am180x in meta-ti?
>>>>>> Did
>>>>>> it solve the missing abi kernel version? Thanks.
>>>>>>
>>>>>> --
>>>>>> Denys
>>>>>
>>>>> Hi Denys,
>>>>>
>>>>> No, I got caught up in something else ... I'll try it tomorrow and report
>>>>> back after I cherry pick that commit Bruce mentioned.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Brian
>>>>
>>>> Update. Not sure if I did this right but this is what I did. I added
>>>> master as a remote and cherry picked
>>>> 02d0a003d603266114512160b209876199241e98. Next I just went for it and
>>>> tried to bitbake my image again and got the same result as before.
>>>> Next I did a bitbake cleanall on virtual/kernel and tried to make my
>>>> image again and still got the same result.
>>>>
>>>> I'm going to leave this build as is and setup a new one using 1.8
>>>> master and see if I get the same thing again. I'll leave this broken
>>>> build alone for a while in case someone wants me to try something with
>>>> it to fix it.
>>>>
>>>> Regards,
>>>>
>>>> Brian
>>>
>>> Yet another update ... I did a fresh checkout of master and tried to
>>> build and had the same kernelabiversion error:
>>>
>>> WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for
>>> now#######################
>>> | ETA:
>>> 00:00:28
>>> WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now
>>> WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for
>>> now########################################
>>>
>>> | ETA: 00:00:26
>>> Parsing recipes: 100%
>>> |##############################################################################################################################################################################|
>>> Time: 00:01:02
>>> Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303
>>> targets, 182 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>> NOTE: multiple providers are available for u-boot (u-boot,
>>> u-boot-glsdk, u-boot-ti-staging)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot
>>> NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
>>> NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
>>>
>>> Build Configuration:
>>> BB_VERSION = "1.27.0"
>>> BUILD_SYS = "x86_64-linux"
>>> NATIVELSBSTRING = "Debian-7.8"
>>> TARGET_SYS = "arm-poky-linux-gnueabi"
>>> MACHINE = "am180x-evm"
>>> DISTRO = "poky"
>>> DISTRO_VERSION = "1.8+snapshot-20150515"
>>> TUNE_FEATURES = "arm armv5 thumb dsp"
>>> TARGET_FPU = "soft"
>>> meta
>>> meta-yocto
>>> meta-yocto-bsp = "master:fab7da4f8030a4067db0522f77eaa6d3b501c68f"
>>> meta-ti = "master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e"
>>> meta-oe
>>> meta-python
>>> meta-networking
>>> meta-webserver = "master:53d55216c8c721d3b66ec8f968737bf081def870"
>>>
>>> NOTE: Preparing RunQueue
>>> NOTE: Executing SetScene Tasks
>>> NOTE: Executing RunQueue Tasks
>>> WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package
>>> apache2-dev requires /usr/bin/perl, but no providers found in its
>>> RDEPENDS [file-rdeps]
>>> ERROR: No kernel-abiversion file found
>>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>>> cannot run depmod, aborting
>>> ERROR: Function failed: do_rootfs
>>> ERROR: Logfile of failure stored in:
>>> /home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/temp/log.do_rootfs.10336
>>> ERROR: Task 7 (/home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs) failed with exit code '1'
>>> NOTE: Tasks Summary: Attempted 2614 tasks of which 9 didn't need to be
>>> rerun and 1 failed.
>>> Waiting for 0 running tasks to finish:
>>>
>>> Summary: 1 task failed:
>>> /home/hutch/yocto_1.8_davinci_2/poky/meta/recipes-core/images/core-image-nodeam.bb,
>>> do_rootfs
>>> Summary: There were 4 WARNING messages shown.
>>> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>>
>> More info for those that care ...
>>
>> The end of the error log file has:
>> DEBUG: Executing python function write_image_manifest
>> DEBUG: Python function write_image_manifest finished
>> NOTE: Executing: ldconfig
>> -r/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/work/am180x_evm-poky-linux-gnueabi/core-image-nodeam/1.0-r0/rootfs-c
>> new -v
>> ERROR: No kernel-abiversion file found
>> (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion),
>> cannot run depmod, aborting
>> DEBUG: Python function do_rootfs finished
>> ERROR: Function failed: do_rootfs
>>
>> I have a linux-dummy director in pkgdata but no kernel-depmod directory exists.
>>
>
> Interesting. Looks like we have some sort of bad dependency. I'm poking around
> to see if I can reproduce this locally.
Brian,
I'm trying to wrap my head around this. Which kernel did you say
was building in your configuration ? Was it really linux-dummy, or
is there a bootable kernel in play ?
Looking at the dependencies, I can see how the depmodwrapper requires
that a kernel be built and the abiversion file created. But in the
case of linux-dummy, there's no header files to use and generate the
abiversion, so it won't be available for depmod.
Which takes me back to one of my original questions, why is depmod
running if the kernel isn't being built as part of this image .. and
that leads me to think I'm missing some important information.
Bruce
>
> Bruce
>
>> Regards,
>>
>> Brian
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
next prev parent reply other threads:[~2015-05-19 16:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 6:49 Migration from 1.7.1 to 1.8 - kernel-abiversion missing Schaumlöffel, Jan
2015-04-28 13:52 ` Bruce Ashfield
2015-04-28 15:36 ` Schaumlöffel, Jan
2015-04-28 18:58 ` Bruce Ashfield
2015-04-29 7:38 ` Schaumlöffel, Jan
2015-04-29 13:23 ` Bruce Ashfield
2015-04-30 7:14 ` Schaumlöffel, Jan
2015-04-30 12:18 ` Bruce Ashfield
2015-04-30 12:27 ` Schaumlöffel, Jan
2015-04-30 14:06 ` Bruce Ashfield
2015-05-11 18:10 ` Brian Hutchinson
2015-05-11 18:10 ` [yocto] " Brian Hutchinson
2015-05-11 18:34 ` Brian Hutchinson
2015-05-11 18:34 ` [yocto] " Brian Hutchinson
2015-05-11 19:06 ` Bruce Ashfield
2015-05-11 19:06 ` [yocto] " Bruce Ashfield
2015-05-12 14:20 ` Brian Hutchinson
2015-05-12 14:20 ` [yocto] " Brian Hutchinson
2015-05-12 15:35 ` Bruce Ashfield
2015-05-12 15:35 ` [yocto] " Bruce Ashfield
2015-05-14 22:08 ` [meta-ti] " Denys Dmytriyenko
2015-05-14 22:08 ` [yocto] " Denys Dmytriyenko
2015-05-14 22:16 ` [meta-ti] " Brian Hutchinson
2015-05-14 22:16 ` [yocto] " Brian Hutchinson
2015-05-15 13:55 ` [meta-ti] " Brian Hutchinson
2015-05-15 13:55 ` [yocto] " Brian Hutchinson
2015-05-15 19:26 ` [meta-ti] " Brian Hutchinson
2015-05-15 19:26 ` [yocto] " Brian Hutchinson
2015-05-15 20:21 ` [meta-ti] " Brian Hutchinson
2015-05-15 20:21 ` [yocto] " Brian Hutchinson
2015-05-19 11:39 ` [meta-ti] " Bruce Ashfield
2015-05-19 11:39 ` [yocto] " Bruce Ashfield
2015-05-19 16:31 ` Bruce Ashfield [this message]
2015-05-19 16:31 ` Bruce Ashfield
2015-05-19 16:42 ` [meta-ti] " Brian Hutchinson
2015-05-19 16:42 ` [yocto] " Brian Hutchinson
2015-05-21 1:49 ` Patricia Holden
2015-06-10 1:12 ` [meta-ti] " Brian Hutchinson
2015-06-10 1:12 ` [yocto] " Brian Hutchinson
2015-06-10 1:14 ` [meta-ti] " Bruce Ashfield
2015-06-10 1:14 ` [yocto] " Bruce Ashfield
2015-06-10 1:34 ` [meta-ti] " Brian Hutchinson
2015-06-10 1:34 ` [yocto] " Brian Hutchinson
2015-06-10 17:32 ` [meta-ti] " Brian Hutchinson
2015-06-10 17:32 ` [yocto] " Brian Hutchinson
2015-06-23 19:15 ` Robert Calhoun
2015-06-23 19:56 ` 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=555B6573.5030002@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=b.hutchman@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-ti@yoctoproject.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.