From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Saul Wold <sgw@linux.intel.com>,
<richard.purdie@linuxfoundation.org>,
"nitin.a.kamble" <nitin.a.kamble@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] linux-yocto/3.10: integrate LTSI
Date: Fri, 07 Feb 2014 09:32:22 -0800 [thread overview]
Message-ID: <CF1A5869.6A760%dvhart@linux.intel.com> (raw)
In-Reply-To: <52F516DC.4080608@windriver.com>
On 2/7/14, 9:24, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>On 14-02-07 11:55 AM, Darren Hart wrote:
>> On 2/7/14, 8:48, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>>>>>>>> | ERROR: Function failed: do_compile (log file is located at
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>/home/pokybuild/yocto-autobuilder-dev/yocto-slave/nightly-x86/build
>>>>>>>>/b
>>>>>>>> ui
>>>>>>>> l
>>>>>>>>
>>>>>>>>
>>>>>>>>d/tmp/work/qemux86-poky-linux/linux-yocto/3.10.25+gitAUTOINC+4d658a
>>>>>>>>a5
>>>>>>>> 80
>>>>>>>> _
>>>>>>>> 78d2a615b1-r0/temp/log.do_compile.1426)
>>
>> So since this is qemux86 that is failing, and Bruce has run the qemu
>> builds - so are we using the right SRCREVs?
>>
>> Machine: 78d2a615b1
>> Meta: 4d658aa580
>
>Sorry for the spam, but is this the same issue that Nitin' fixed
>upstream that that I integrated this week ? I have another pending
>commit that updates the SRCREVs again, but I was waiting on LTSI to
>make it in before sending it.
No, this is failing with:
| drivers/built-in.o: In function `gen6_update_ring_freq':
|
/build/yocto/master/qemux86_20140207091321/build/tmp/work/qemux86-poky-linu
x/linux-yocto/3.10.25+gitAUTOINC+4d658aa580_78d2a615b1-r0/linux/drivers/gpu
/drm/i915/intel_pm.c:3876: undefined reference to `cpufreq_cpu_get'
|
/build/yocto/master/qemux86_20140207091321/build/tmp/work/qemux86-poky-linu
x/linux-yocto/3.10.25+gitAUTOINC+4d658aa580_78d2a615b1-r0/linux/drivers/gpu
/drm/i915/intel_pm.c:3879: undefined reference to `cpufreq_cpu_put'
The Kconfig fix from Nitin was for generic_chip.c, this is for i915 and pm.
I'll update SRCREVs and see if this resolves itself.
--
Darren
next prev parent reply other threads:[~2014-02-07 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 17:34 [PATCH 0/2] kernel: consolidated pull request Bruce Ashfield
2014-02-04 17:34 ` [PATCH 1/2] kernel: stop using -exec rm for deleting files Bruce Ashfield
2014-02-04 23:26 ` Richard Purdie
2014-02-05 0:35 ` Bruce Ashfield
2014-02-05 1:36 ` Paul Barker
2014-02-05 3:10 ` Bruce Ashfield
2014-02-09 12:06 ` Richard Purdie
2014-02-09 14:36 ` Bruce Ashfield
2014-02-10 13:32 ` Bruce Ashfield
2014-02-10 17:17 ` Bruce Ashfield
2014-02-10 17:23 ` Richard Purdie
2014-02-04 17:34 ` [PATCH 2/2] linux-yocto/3.10: integrate LTSI Bruce Ashfield
2014-02-07 16:42 ` Saul Wold
2014-02-07 16:44 ` Bruce Ashfield
2014-02-07 16:46 ` Darren Hart
2014-02-07 16:47 ` Darren Hart
2014-02-07 16:48 ` Bruce Ashfield
2014-02-07 16:55 ` Darren Hart
2014-02-07 16:57 ` Bruce Ashfield
2014-02-07 17:24 ` Bruce Ashfield
2014-02-07 17:32 ` Darren Hart [this message]
2014-02-07 19:22 ` 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=CF1A5869.6A760%dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=sgw@linux.intel.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 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.