Skip to contentSkip to conversation

linux-yocto/5.10: update qemuriscv32 v5.10.23

PATCH In review Bruce Ashfield 2 participants 6 messages Mar 22, 2021 – Mar 23, 2021

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 linux-yocto/5.10: update qemuriscv32 v5.10.23

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -1
index 9c122832f4..83e70d01d1 100644
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
 SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
 SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
 SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
 SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
 SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
 SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"
Signature · 1 line
2.19.1
#1 lore raw
Quoted 17 lines · Bruce Ashfield

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
  meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +0 -0
index 9c122832f4..83e70d01d1 100644

meta/recipes-kernel/linux/linux-yocto_5.10.bb SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" · line 24

Quoted 8 lines
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
  SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"

I wonder if we really need to lock the machines using tip of v5.10/standard/base e.g. x86/x86_64/ppc64/rv64/rv32

Quoted 4 lines
#2 lore raw
Quoted 24 lines · Khem Raj
Quoted 20 lines · Bruce Ashfield

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
  meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +0 -1
index 9c122832f4..83e70d01d1 100644
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
  SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
Quoted 8 lines

meta/recipes-kernel/linux/linux-yocto_5.10.bb SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" · line 24

Quoted 5 lines
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -0
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
  SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"

I wonder if we really need to lock the machines using tip of v5.10/standard/base e.g. x86/x86_64/ppc64/rv64/rv32

I'm not sure I understand the question / comment.

They are on the tip of that branch now, but still must be separately specified so we have the individual control as needed.

But they all do need to walk forward at the same pace. Every -stable goes to all BSP branches. Supporting them on different versions just isn't sane.

Cheers,

Bruce

Quoted 4 lines
Quoted 4 lines
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
#3 lore raw
Quoted 34 lines · Bruce Ashfield
Quoted 24 lines · Khem Raj
Quoted 20 lines · Bruce Ashfield

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
   meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +0 -1
index 9c122832f4..83e70d01d1 100644
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
   SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
Quoted 8 lines

meta/recipes-kernel/linux/linux-yocto_5.10.bb SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" · line 24

Quoted 5 lines
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -0
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"

I wonder if we really need to lock the machines using tip of v5.10/standard/base e.g. x86/x86_64/ppc64/rv64/rv32

Quoted 1 line

I'm not sure I understand the question / comment.

SRCREV for the machines are said is same and perhaps branch too. So I was saying if this perhaps is not required to set the SRCREV per machine for such machines.

Quoted 19 lines

They are on the tip of that branch now, but still must be separately specified so we have the individual control as needed.

But they all do need to walk forward at the same pace. Every -stable goes to all BSP branches. Supporting them on different versions just isn't sane.

Cheers,

Bruce

Quoted 4 lines
Quoted 4 lines
#4 lore raw
Quoted 38 lines · Khem Raj
Quoted 34 lines · Bruce Ashfield
Quoted 32 lines · Khem Raj
Quoted 17 lines · Bruce Ashfield

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
   meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +0 -0
index 9c122832f4..83e70d01d1 100644

meta/recipes-kernel/linux/linux-yocto_5.10.bb SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" · line 24

Quoted 8 lines
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
   SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"

I wonder if we really need to lock the machines using tip of v5.10/standard/base e.g. x86/x86_64/ppc64/rv64/rv32

Quoted 5 lines
Quoted 1 line

I'm not sure I understand the question / comment.

SRCREV for the machines are said is same and perhaps branch too. So I was saying if this perhaps is not required to set the SRCREV per machine for such machines.

It's automatic once in my update scripts (which it is now), and I'd rather be explicit on these, since the machine overrides are both flexible and self-documentation.

There won't be any future individual bumps of this, it'll just be done along with everything else.

Cheers,

Bruce

Quoted 20 lines
Quoted 20 lines

They are on the tip of that branch now, but still must be separately specified so we have the individual control as needed.

But they all do need to walk forward at the same pace. Every -stable goes to all BSP branches. Supporting them on different versions just isn't sane.

Cheers,

Bruce

Quoted 4 lines
Quoted 4 lines
Signature · 3 lines
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
#5 lore raw
Quoted 46 lines · Bruce Ashfield
Quoted 38 lines · Khem Raj
Quoted 34 lines · Bruce Ashfield
Quoted 32 lines · Khem Raj
Quoted 17 lines · Bruce Ashfield

From: Bruce Ashfield <[email protected]>

The kernel SRCREV updates were missing riscv32, so stayed back on 5.10.21, which causes build issues as PV is out of sync with the actual kernel version.

---
   meta/recipes-kernel/linux/linux-yocto_5.10.bb | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-kernel/linux/linux-yocto_5.10.bb +0 -0
index 9c122832f4..83e70d01d1 100644

meta/recipes-kernel/linux/linux-yocto_5.10.bb SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd" · line 24

Quoted 8 lines
meta/recipes-kernel/linux/linux-yocto_5.10.bb +1 -1
@@ -18,7 +18,7 @@ SRCREV_machine_qemuarm64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips ?= "68527a50a2f5b0992ba85255325d76a9f187c237"
   SRCREV_machine_qemuppc ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemuriscv64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
-SRCREV_machine_qemuriscv32 ?= "8c516ced69f41563404ada0bea315a55bcf1df6f"
+SRCREV_machine_qemuriscv32 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemux86-64 ?= "04a11eb4aec4efe3064f27b207e8a41c28bb08cd"
   SRCREV_machine_qemumips64 ?= "c19b50af1e3680ff6050a0cce8dcd888accafd9b"

I wonder if we really need to lock the machines using tip of v5.10/standard/base e.g. x86/x86_64/ppc64/rv64/rv32

Quoted 5 lines
Quoted 1 line

I'm not sure I understand the question / comment.

SRCREV for the machines are said is same and perhaps branch too. So I was saying if this perhaps is not required to set the SRCREV per machine for such machines.

Quoted 6 lines

It's automatic once in my update scripts (which it is now), and I'd rather be explicit on these, since the machine overrides are both flexible and self-documentation.

There won't be any future individual bumps of this, it'll just be done along with everything else.

Totally fine.
Yeah explicit is better, I was just suggesting if it was not an automated process
as it can add another manual error point.

Quoted 32 lines

Cheers,

Bruce

Quoted 11 lines
Quoted 11 lines

They are on the tip of that branch now, but still must be separately specified so we have the individual control as needed.

But they all do need to walk forward at the same pace. Every -stable goes to all BSP branches. Supporting them on different versions just isn't sane.

Cheers,

Quoted 9 lines
Quoted 9 lines

Bruce

Quoted 4 lines
Quoted 4 lines

--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end
- "Use the force Harry" - Gandalf, Star Trek II