Patchwork linux-libc-headers: updated to 3.4.3

login
register
mail settings
Submitter Bogdan Marinescu
Date July 11, 2012, 1:02 p.m.
Message ID <1342011739-6416-1-git-send-email-bogdan.a.marinescu@intel.com>
Download mbox | patch
Permalink /patch/31751/
State Accepted
Commit d67e47bd457de90b19428245644dc64ecf4ba11a
Headers show

Comments

Bogdan Marinescu - July 11, 2012, 1:02 p.m.
Tested by building core-image-sato-sdk.

Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
---
 meta/conf/distro/include/tcmode-default.inc        |    2 +-
 .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
 .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
 3 files changed, 7 insertions(+), 7 deletions(-)
 create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
 delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
Saul Wold - July 17, 2012, 3:58 p.m.
On 07/11/2012 06:02 AM, Bogdan Marinescu wrote:
> Tested by building core-image-sato-sdk.
>
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
>   meta/conf/distro/include/tcmode-default.inc        |    2 +-
>   .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>   .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>   3 files changed, 7 insertions(+), 7 deletions(-)
>   create mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>   delete mode 100644 meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
> index f11e687..0a068be 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>   BINUVERSION ?= "2.22"
>   EGLIBCVERSION ?= "2.15"
>   UCLIBCVERSION ?= "0.9.33"
> -LINUXLIBCVERSION ?= "3.4"
> +LINUXLIBCVERSION ?= "3.4.3"
>
>   PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>   PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
> diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
> new file mode 100644
> index 0000000..6f8d9e8
> --- /dev/null
> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
> @@ -0,0 +1,6 @@
> +require linux-libc-headers.inc
> +
> +PR = "r0"
> +
> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
> +SRC_URI[sha256sum] = "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
> diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> deleted file mode 100644
> index 9e8c88f..0000000
> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -require linux-libc-headers.inc
> -
> -PR = "r0"
> -
> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
> -SRC_URI[sha256sum] = "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
>
Merged into OE-Core

Thanks
	Sau!
Khem Raj - July 17, 2012, 4:54 p.m.
Why is recipe renamed

On Wednesday, July 11, 2012, Bogdan Marinescu <bogdan.a.marinescu@intel.com>
wrote:
> Tested by building core-image-sato-sdk.
>
> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> ---
>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>  .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>  .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>  3 files changed, 7 insertions(+), 7 deletions(-)
>  create mode 100644 meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.3.bb
>  delete mode 100644 meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.bb
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
> index f11e687..0a068be 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>  BINUVERSION ?= "2.22"
>  EGLIBCVERSION ?= "2.15"
>  UCLIBCVERSION ?= "0.9.33"
> -LINUXLIBCVERSION ?= "3.4"
> +LINUXLIBCVERSION ?= "3.4.3"
>
>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
> diff --git a/meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.3.bb b/meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.3.bb
> new file mode 100644
> index 0000000..6f8d9e8
> --- /dev/null
> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
> @@ -0,0 +1,6 @@
> +require linux-libc-headers.inc
> +
> +PR = "r0"
> +
> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
> +SRC_URI[sha256sum] =
"17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
> diff --git a/meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.bb b/meta/recipes-kernel/linux-libc-headers/
linux-libc-headers_3.4.bb
> deleted file mode 100644
> index 9e8c88f..0000000
> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -require linux-libc-headers.inc
> -
> -PR = "r0"
> -
> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
> -SRC_URI[sha256sum] =
"a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
> --
> 1.7.9.5
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Bogdan Marinescu - July 18, 2012, 11:30 a.m.
On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> Why is recipe renamed

Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?

>
>
> On Wednesday, July 11, 2012, Bogdan Marinescu <bogdan.a.marinescu@intel.com>
> wrote:
>> Tested by building core-image-sato-sdk.
>>
>> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>> ---
>>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>  .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>>  .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>>  3 files changed, 7 insertions(+), 7 deletions(-)
>>  create mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>  delete mode 100644
>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>
>> diff --git a/meta/conf/distro/include/tcmode-default.inc
>> b/meta/conf/distro/include/tcmode-default.inc
>> index f11e687..0a068be 100644
>> --- a/meta/conf/distro/include/tcmode-default.inc
>> +++ b/meta/conf/distro/include/tcmode-default.inc
>> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>>  BINUVERSION ?= "2.22"
>>  EGLIBCVERSION ?= "2.15"
>>  UCLIBCVERSION ?= "0.9.33"
>> -LINUXLIBCVERSION ?= "3.4"
>> +LINUXLIBCVERSION ?= "3.4.3"
>>
>>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
>> diff --git
>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>> new file mode 100644
>> index 0000000..6f8d9e8
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>> @@ -0,0 +1,6 @@
>> +require linux-libc-headers.inc
>> +
>> +PR = "r0"
>> +
>> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
>> +SRC_URI[sha256sum] =
>> "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
>> diff --git
>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>> deleted file mode 100644
>> index 9e8c88f..0000000
>> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>> +++ /dev/null
>> @@ -1,6 +0,0 @@
>> -require linux-libc-headers.inc
>> -
>> -PR = "r0"
>> -
>> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
>> -SRC_URI[sha256sum] =
>> "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
Bruce Ashfield - July 18, 2012, 1:03 p.m.
On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
<bogdan.a.marinescu@intel.com> wrote:
> On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> Why is recipe renamed
>
> Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?

No one replied to my other question (or at least no one replied that I
noticed), about
why we even bothered to bump it to 3.4.3 ...

I have the same elements in that question .. but from a different angle.

Cheers,

Bruce

>
>>
>>
>> On Wednesday, July 11, 2012, Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>> wrote:
>>> Tested by building core-image-sato-sdk.
>>>
>>> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>>> ---
>>>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>  .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>>>  .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>>>  3 files changed, 7 insertions(+), 7 deletions(-)
>>>  create mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>  delete mode 100644
>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>
>>> diff --git a/meta/conf/distro/include/tcmode-default.inc
>>> b/meta/conf/distro/include/tcmode-default.inc
>>> index f11e687..0a068be 100644
>>> --- a/meta/conf/distro/include/tcmode-default.inc
>>> +++ b/meta/conf/distro/include/tcmode-default.inc
>>> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>>>  BINUVERSION ?= "2.22"
>>>  EGLIBCVERSION ?= "2.15"
>>>  UCLIBCVERSION ?= "0.9.33"
>>> -LINUXLIBCVERSION ?= "3.4"
>>> +LINUXLIBCVERSION ?= "3.4.3"
>>>
>>>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>>>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
>>> diff --git
>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>> new file mode 100644
>>> index 0000000..6f8d9e8
>>> --- /dev/null
>>> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>> @@ -0,0 +1,6 @@
>>> +require linux-libc-headers.inc
>>> +
>>> +PR = "r0"
>>> +
>>> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
>>> +SRC_URI[sha256sum] =
>>> "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
>>> diff --git
>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>> deleted file mode 100644
>>> index 9e8c88f..0000000
>>> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>> +++ /dev/null
>>> @@ -1,6 +0,0 @@
>>> -require linux-libc-headers.inc
>>> -
>>> -PR = "r0"
>>> -
>>> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
>>> -SRC_URI[sha256sum] =
>>> "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
>>> --
>>> 1.7.9.5
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Bogdan Marinescu - July 18, 2012, 1:17 p.m.
On Wed, Jul 18, 2012 at 4:03 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
> <bogdan.a.marinescu@intel.com> wrote:
>> On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> Why is recipe renamed
>>
>> Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
>
> No one replied to my other question (or at least no one replied that I
> noticed), about
> why we even bothered to bump it to 3.4.3 ...

Quite simply, I'm the owner of the recipe and I'm supposed to upgrade
it when a new version appears :)

Best,
Bogdan

>
> I have the same elements in that question .. but from a different angle.
>
> Cheers,
>
> Bruce
>
>>
>>>
>>>
>>> On Wednesday, July 11, 2012, Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>>> wrote:
>>>> Tested by building core-image-sato-sdk.
>>>>
>>>> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>>>> ---
>>>>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>  .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>>>>  .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>>>>  3 files changed, 7 insertions(+), 7 deletions(-)
>>>>  create mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>>  delete mode 100644
>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>>
>>>> diff --git a/meta/conf/distro/include/tcmode-default.inc
>>>> b/meta/conf/distro/include/tcmode-default.inc
>>>> index f11e687..0a068be 100644
>>>> --- a/meta/conf/distro/include/tcmode-default.inc
>>>> +++ b/meta/conf/distro/include/tcmode-default.inc
>>>> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>>>>  BINUVERSION ?= "2.22"
>>>>  EGLIBCVERSION ?= "2.15"
>>>>  UCLIBCVERSION ?= "0.9.33"
>>>> -LINUXLIBCVERSION ?= "3.4"
>>>> +LINUXLIBCVERSION ?= "3.4.3"
>>>>
>>>>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>>>>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
>>>> diff --git
>>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>> new file mode 100644
>>>> index 0000000..6f8d9e8
>>>> --- /dev/null
>>>> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>> @@ -0,0 +1,6 @@
>>>> +require linux-libc-headers.inc
>>>> +
>>>> +PR = "r0"
>>>> +
>>>> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
>>>> +SRC_URI[sha256sum] =
>>>> "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
>>>> diff --git
>>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>> deleted file mode 100644
>>>> index 9e8c88f..0000000
>>>> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>> +++ /dev/null
>>>> @@ -1,6 +0,0 @@
>>>> -require linux-libc-headers.inc
>>>> -
>>>> -PR = "r0"
>>>> -
>>>> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
>>>> -SRC_URI[sha256sum] =
>>>> "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
>>>> --
>>>> 1.7.9.5
>>>>
>>>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Bruce Ashfield - July 18, 2012, 1:23 p.m.
On Wed, Jul 18, 2012 at 9:17 AM, Marinescu, Bogdan A
<bogdan.a.marinescu@intel.com> wrote:
> On Wed, Jul 18, 2012 at 4:03 PM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
>> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
>> <bogdan.a.marinescu@intel.com> wrote:
>>> On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>> Why is recipe renamed
>>>
>>> Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
>>
>> No one replied to my other question (or at least no one replied that I
>> noticed), about
>> why we even bothered to bump it to 3.4.3 ...
>
> Quite simply, I'm the owner of the recipe and I'm supposed to upgrade
> it when a new version appears :)

I must have missed that .. because I'd disagree with both counts.

 - libc-headers does not need to be upgraded with every korg stable update
 - it is coupled to the kernel, and I've done it in the past, and had planned to
   leave it a 3.4.

Cheers,

Bruce

>
> Best,
> Bogdan
>
>>
>> I have the same elements in that question .. but from a different angle.
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>>>
>>>>
>>>> On Wednesday, July 11, 2012, Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>>>> wrote:
>>>>> Tested by building core-image-sato-sdk.
>>>>>
>>>>> Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com>
>>>>> ---
>>>>>  meta/conf/distro/include/tcmode-default.inc        |    2 +-
>>>>>  .../linux-libc-headers/linux-libc-headers_3.4.3.bb |    6 ++++++
>>>>>  .../linux-libc-headers/linux-libc-headers_3.4.bb   |    6 ------
>>>>>  3 files changed, 7 insertions(+), 7 deletions(-)
>>>>>  create mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>>>  delete mode 100644
>>>>> meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>>>
>>>>> diff --git a/meta/conf/distro/include/tcmode-default.inc
>>>>> b/meta/conf/distro/include/tcmode-default.inc
>>>>> index f11e687..0a068be 100644
>>>>> --- a/meta/conf/distro/include/tcmode-default.inc
>>>>> +++ b/meta/conf/distro/include/tcmode-default.inc
>>>>> @@ -22,7 +22,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
>>>>>  BINUVERSION ?= "2.22"
>>>>>  EGLIBCVERSION ?= "2.15"
>>>>>  UCLIBCVERSION ?= "0.9.33"
>>>>> -LINUXLIBCVERSION ?= "3.4"
>>>>> +LINUXLIBCVERSION ?= "3.4.3"
>>>>>
>>>>>  PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
>>>>>  PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
>>>>> diff --git
>>>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>>> new file mode 100644
>>>>> index 0000000..6f8d9e8
>>>>> --- /dev/null
>>>>> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
>>>>> @@ -0,0 +1,6 @@
>>>>> +require linux-libc-headers.inc
>>>>> +
>>>>> +PR = "r0"
>>>>> +
>>>>> +SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
>>>>> +SRC_URI[sha256sum] =
>>>>> "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
>>>>> diff --git
>>>>> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>>> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>>> deleted file mode 100644
>>>>> index 9e8c88f..0000000
>>>>> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
>>>>> +++ /dev/null
>>>>> @@ -1,6 +0,0 @@
>>>>> -require linux-libc-headers.inc
>>>>> -
>>>>> -PR = "r0"
>>>>> -
>>>>> -SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
>>>>> -SRC_URI[sha256sum] =
>>>>> "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"
>>>>> --
>>>>> 1.7.9.5
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Openembedded-core mailing list
>>>>> Openembedded-core@lists.openembedded.org
>>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await
>> thee at its end"
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Richard Purdie - July 18, 2012, 1:23 p.m.
On Wed, 2012-07-18 at 09:03 -0400, Bruce Ashfield wrote:
> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
> <bogdan.a.marinescu@intel.com> wrote:
> > On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> Why is recipe renamed
> >
> > Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
> 
> No one replied to my other question (or at least no one replied that I
> noticed), about
> why we even bothered to bump it to 3.4.3 ...
> 
> I have the same elements in that question .. but from a different angle.

I think Khem's question is a little vague and I'm not sure how I'd
answer that.

As for policy of updating the kernel headers against stable releases, it
can't hurt and we needed to bump PV or PR anyway as Martin mentioned so
that was the main reason I took the patch.

I think there could be a perception issue if we don't update, on the
other hand it could be considered unnecessary churn. So I think in
future this will be on a case by case basis. If there was a header fix
in the stable series (which is conceivable), we would want to take that
for example.

Cheers,

Richard
Bruce Ashfield - July 18, 2012, 1:27 p.m.
On Wed, Jul 18, 2012 at 9:23 AM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2012-07-18 at 09:03 -0400, Bruce Ashfield wrote:
>> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
>> <bogdan.a.marinescu@intel.com> wrote:
>> > On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> >> Why is recipe renamed
>> >
>> > Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
>>
>> No one replied to my other question (or at least no one replied that I
>> noticed), about
>> why we even bothered to bump it to 3.4.3 ...
>>
>> I have the same elements in that question .. but from a different angle.
>
> I think Khem's question is a little vague and I'm not sure how I'd
> answer that.
>
> As for policy of updating the kernel headers against stable releases, it
> can't hurt and we needed to bump PV or PR anyway as Martin mentioned so
> that was the main reason I took the patch.
>
> I think there could be a perception issue if we don't update, on the
> other hand it could be considered unnecessary churn. So I think in
> future this will be on a case by case basis. If there was a header fix
> in the stable series (which is conceivable), we would want to take that
> for example.

This works for me, and was my main point. Updating it is one thing, but
we should consider before updating, since the "normal" rules don't always
apply to this particular package.

Thanks for the clarification,

Bruce

>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Richard Purdie - July 18, 2012, 1:50 p.m.
On Wed, 2012-07-18 at 09:23 -0400, Bruce Ashfield wrote:
> On Wed, Jul 18, 2012 at 9:17 AM, Marinescu, Bogdan A
> <bogdan.a.marinescu@intel.com> wrote:
> > On Wed, Jul 18, 2012 at 4:03 PM, Bruce Ashfield
> > <bruce.ashfield@gmail.com> wrote:
> >> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
> >> <bogdan.a.marinescu@intel.com> wrote:
> >>> On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >>>> Why is recipe renamed
> >>>
> >>> Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
> >>
> >> No one replied to my other question (or at least no one replied that I
> >> noticed), about
> >> why we even bothered to bump it to 3.4.3 ...
> >
> > Quite simply, I'm the owner of the recipe and I'm supposed to upgrade
> > it when a new version appears :)
> 
> I must have missed that .. because I'd disagree with both counts.
> 
>  - libc-headers does not need to be upgraded with every korg stable update
>  - it is coupled to the kernel, and I've done it in the past, and had planned to
>    leave it a 3.4.

Bogdan: This is probably one of the cases we shouldn't automatically
update just based on the output of the version checking scripts. We
should only change the point release version here if there is a change
to the kernel headers that we need.

As for the recipe owner, this one may be best owned by Bruce but I'm
open minded on that.


Cheers,

Richard
Bogdan Marinescu - July 18, 2012, 1:52 p.m.
On Wed, Jul 18, 2012 at 4:50 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Wed, 2012-07-18 at 09:23 -0400, Bruce Ashfield wrote:
>> On Wed, Jul 18, 2012 at 9:17 AM, Marinescu, Bogdan A
>> <bogdan.a.marinescu@intel.com> wrote:
>> > On Wed, Jul 18, 2012 at 4:03 PM, Bruce Ashfield
>> > <bruce.ashfield@gmail.com> wrote:
>> >> On Wed, Jul 18, 2012 at 7:30 AM, Marinescu, Bogdan A
>> >> <bogdan.a.marinescu@intel.com> wrote:
>> >>> On Tue, Jul 17, 2012 at 7:54 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> >>>> Why is recipe renamed
>> >>>
>> >>> Wasn't I supposed to do that when I upgraded the package from 3.4 to 3.4.3 ?
>> >>
>> >> No one replied to my other question (or at least no one replied that I
>> >> noticed), about
>> >> why we even bothered to bump it to 3.4.3 ...
>> >
>> > Quite simply, I'm the owner of the recipe and I'm supposed to upgrade
>> > it when a new version appears :)
>>
>> I must have missed that .. because I'd disagree with both counts.
>>
>>  - libc-headers does not need to be upgraded with every korg stable update
>>  - it is coupled to the kernel, and I've done it in the past, and had planned to
>>    leave it a 3.4.
>
> Bogdan: This is probably one of the cases we shouldn't automatically
> update just based on the output of the version checking scripts. We
> should only change the point release version here if there is a change
> to the kernel headers that we need.

Understood, thanks.

>
> As for the recipe owner, this one may be best owned by Bruce but I'm
> open minded on that.

I have absolutely nothing against that.

Thanks,
Bogdan

>
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Patch

diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc
index f11e687..0a068be 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -22,7 +22,7 @@  SDKGCCVERSION ?= "${GCCVERSION}"
 BINUVERSION ?= "2.22"
 EGLIBCVERSION ?= "2.15"
 UCLIBCVERSION ?= "0.9.33"
-LINUXLIBCVERSION ?= "3.4"
+LINUXLIBCVERSION ?= "3.4.3"
 
 PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
 PREFERRED_VERSION_gcc-cross ?= "${GCCVERSION}"
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
new file mode 100644
index 0000000..6f8d9e8
--- /dev/null
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.3.bb
@@ -0,0 +1,6 @@ 
+require linux-libc-headers.inc
+
+PR = "r0"
+
+SRC_URI[md5sum] = "3aefa02db55715d627ed23a01667057d"
+SRC_URI[sha256sum] = "17f1256daa289dde1a0a587c9753556d37a52770f7c4efcf2666fd4796a6eacc"
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
deleted file mode 100644
index 9e8c88f..0000000
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_3.4.bb
+++ /dev/null
@@ -1,6 +0,0 @@ 
-require linux-libc-headers.inc
-
-PR = "r0"
-
-SRC_URI[md5sum] = "146af0160fc7a60cf9acf44aec13482b"
-SRC_URI[sha256sum] = "a797a15d0b6228381507c14ecf4eec4a6cc5c77cfd521ba3b3e1325e85b5b16d"