This is good, it has passed my local tests, no new warnings were introduced.

Bruce

On Mon, Apr 4, 2022 at 3:20 PM Bruce Ashfield via lists.openembedded.org
<[email protected]> wrote:

> I've heard this may be causing warnings on some configurations.
>
> I'm re-testing this now, and will follow up one way or the other. But
> until then, there's no sense queuing them.
>
> Bruce
>
> On Mon, Apr 4, 2022 at 11:19 AM <[email protected]> wrote:
>
>> From: Bruce Ashfield <[email protected]>
>>
>> Integrating the following commit(s) to linux-yocto/.:
>>
>>     63e25b57177 features/security: Move x86_64 configs to separate file
>>
>> Signed-off-by: Kamil Dziezyk <[email protected]>
>> Signed-off-by: Bruce Ashfield <[email protected]>
>> ---
>>  meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb   | 2 +-
>>  meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 2 +-
>>  meta/recipes-kernel/linux/linux-yocto_5.15.bb      | 2 +-
>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
>> b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
>> index 73a720d348..87ccfc1f45 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
>> @@ -12,7 +12,7 @@ python () {
>>  }
>>
>>  SRCREV_machine ?= "29d051cc421a76432897019edc33edae35b16e39"
>> -SRCREV_meta ?= "7dd85143b4ed77bdcb6628ac8ea69917e1cd29e5"
>> +SRCREV_meta ?= "63e25b5717751b4b33685bd5991d10c52934a4c6"
>>
>>  SRC_URI = "git://
>> git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine
>> <http://git.yoctoproject.org/linux-yocto.git;branch=$%7BKBRANCH%7D;name=machine>
>> \
>>             git://
>> git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}
>> <http://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=$%7BKMETA%7D>
>> "
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
>> b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
>> index d5b301b4d5..d8ce5dc518 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
>> @@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
>>
>>  SRCREV_machine:qemuarm ?= "cc9e92e826af229b841fcaf8c645e638a86eba43"
>>  SRCREV_machine ?= "c3d54a67cbf3fb8e6df2d88c80e9d2c74f69aba4"
>> -SRCREV_meta ?= "7dd85143b4ed77bdcb6628ac8ea69917e1cd29e5"
>> +SRCREV_meta ?= "63e25b5717751b4b33685bd5991d10c52934a4c6"
>>
>>  PV = "${LINUX_VERSION}+git${SRCPV}"
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb
>> b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
>> index b936257aa7..54157fd245 100644
>> --- a/meta/recipes-kernel/linux/linux-yocto_5.15.bb
>> +++ b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
>> @@ -23,7 +23,7 @@ SRCREV_machine:qemux86 ?=
>> "c9f3902d8069e32a8928153a38d8f6115194d128"
>>  SRCREV_machine:qemux86-64 ?= "c9f3902d8069e32a8928153a38d8f6115194d128"
>>  SRCREV_machine:qemumips64 ?= "a4805fe749c9c56d18a60b5378674760ef0e85ed"
>>  SRCREV_machine ?= "c9f3902d8069e32a8928153a38d8f6115194d128"
>> -SRCREV_meta ?= "7dd85143b4ed77bdcb6628ac8ea69917e1cd29e5"
>> +SRCREV_meta ?= "63e25b5717751b4b33685bd5991d10c52934a4c6"
>>
>>  # set your preferred provider of linux-yocto to 'linux-yocto-upstream',
>> and you'll
>>  # get the <version>/base branch, which is pure upstream -stable, and the
>> same
>> --
>> 2.19.1
>>
>>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
>
> 
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164010): 
https://lists.openembedded.org/g/openembedded-core/message/164010
Mute This Topic: https://lists.openembedded.org/mt/90244246/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to