From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] libc-headers: set TC default to 3.14
Date: Tue, 1 Apr 2014 10:52:50 -0400 [thread overview]
Message-ID: <533AD2C2.7000104@windriver.com> (raw)
In-Reply-To: <20140401145014.GQ2425@jama>
On 14-04-01 10:50 AM, Martin Jansa wrote:
> On Tue, Apr 01, 2014 at 08:54:42AM -0400, Bruce Ashfield wrote:
>> On 14-04-01 02:42 AM, Khem Raj wrote:
>>>
>>> On Mar 31, 2014, at 12:50 PM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>>>
>>>>> i dont believe you tested all layer combinations
>>>>
>>>> I've tested everything I can, as has the autobuilder. I can't offer
>>>> any more than this.
>>>>
>>>>>>
>>>>>>
>>>>>>> at this point. 3.10 being LTS
>>>>>>> I would assume its a better option to keep at 3.10
>>>>>>
>>>>>>
>>>>>> I disagree, this is consistent with other releases and the documented
>>>>>> plan of action. I'd rather not have a massive version jump in the fall.
>>>>>
>>>>> its probably not a bad option to stick to LTS version for kernel headers
>>>>> after all
>>>>
>>>> Again, I disagree.
>>>>
>>>> We can maybe keep the 3.10 recipe around,
>>>
>>> Thats ugly too. We decided to stick to one version of headers last time.
>>>
>>>> but the default should
>>>> be 3.14, we need a matched kernel and libc-headers to get the best integration
>>>> and leveraging of the latest features.
>>>>
>>>> If we pull the headers, pull the kernel.
>>>
>>> this all is understood, however we have to get better with timings especially
>>> changing something like kernel headers whose impact is far reaching then
>>> just updating kernel proper.
>>
>> We do the best we can and I can only play the timing that is dealt
>> by the upstream projects ... but we all know that!
>>
>> We arranged for as much soak testing and building as we could behind
>> the scenes.
>>
>> That being said, we are going to introduce the versioned kernel and
>> libc-headers recipes in the -rc1 timeframe next time around and we
>> captured that intention on the kernel planning wiki for 1.7 .. so that
>> should help in the next cycle.
>
> This failure also seems new:
>
> |
> /home/jenkins/oe/shr-core-branches/shr-core/tmp-eglibc/work/qemuarm-oe-linux-gnueabi/lttng-modules/2.3.3-r0/git/probes/../instrumentation/events/lttng-module/../../../probes/../instrumentation/events/lttng-module/block.h:344:24:
> error: 'struct bio' has no member named 'bi_sector'
> | tp_assign(sector, bio->bi_sector)
For qemuarm. Hmm. I did build lttng modules for it here, as I presume
the autobuilder did as well.
But I'll launch another build to see what happens here.
Bruce
> | ^
>
next prev parent reply other threads:[~2014-04-01 14:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 17:56 [PATCH 0/5] lnux-yocto: 3.14 updates Bruce Ashfield
2014-03-31 17:56 ` [PATCH 1/5] linux-yocto/3.14: introduce versioned recipes Bruce Ashfield
2014-03-31 19:39 ` Paul Barker
2014-03-31 19:41 ` Bruce Ashfield
2014-03-31 17:56 ` [PATCH 2/5] linux-libc-headers: make compression format configurable Bruce Ashfield
2014-03-31 17:56 ` [PATCH 3/5] linux-libc-headers: add 3.14 libc headers Bruce Ashfield
2014-03-31 17:56 ` [PATCH 4/5] libc-headers: set TC default to 3.14 Bruce Ashfield
2014-03-31 19:29 ` Khem Raj
2014-03-31 19:33 ` Bruce Ashfield
2014-03-31 19:47 ` Khem Raj
2014-03-31 19:50 ` Bruce Ashfield
2014-04-01 6:42 ` Khem Raj
2014-04-01 12:54 ` Bruce Ashfield
2014-04-01 14:50 ` Martin Jansa
2014-04-01 14:52 ` Bruce Ashfield [this message]
2014-04-01 14:54 ` Richard Purdie
2014-04-01 15:41 ` Bruce Ashfield
2014-03-31 17:56 ` [PATCH 5/5] linux-libc-headers: remove 3.10 recipe Bruce Ashfield
2014-03-31 21:09 ` [PATCH 0/5] lnux-yocto: 3.14 updates Bruce Ashfield
2014-03-31 22:30 ` 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=533AD2C2.7000104@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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