From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH v5 3/5] linux-mainline: update from 4.19.0 to 4.19.88
Date: Tue, 10 Dec 2019 19:22:06 +0100 [thread overview]
Message-ID: <645fd80af21adcf3983a1a9ed24746557727c4e7.1576002128.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1576002128.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1576002128.git.jan.kiszka@siemens.com>
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
In preparation for a new machine addition, update the linux-mainline
kernel from 4.19.0 to 4.19.88. This is needed to get some of the mips
fixes that were integrated in this longterm kernel version (and in
particular: MIPS: have "plain" make calls build dtbs for selected
platforms, i.e. 637dfa0fad6d91a9a709dc70549a6d20fa77f615 upstream)
Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
[Jan: refresh from .80 to .88]
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../linux/{linux-mainline_4.19.0.bb => linux-mainline_4.19.88.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-isar/recipes-kernel/linux/{linux-mainline_4.19.0.bb => linux-mainline_4.19.88.bb} (87%)
diff --git a/meta-isar/recipes-kernel/linux/linux-mainline_4.19.0.bb b/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
similarity index 87%
rename from meta-isar/recipes-kernel/linux/linux-mainline_4.19.0.bb
rename to meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
index 127f6e2..695eb39 100644
--- a/meta-isar/recipes-kernel/linux/linux-mainline_4.19.0.bb
+++ b/meta-isar/recipes-kernel/linux/linux-mainline_4.19.88.bb
@@ -12,7 +12,7 @@ ARCHIVE_VERSION = "${@ d.getVar('PV')[:-2] if d.getVar('PV').endswith('.0') else
SRC_URI += " \
https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-${ARCHIVE_VERSION}.tar.xz \
file://x86_64_defconfig"
-SRC_URI[sha256sum] = "0c68f5655528aed4f99dae71a5b259edc93239fa899e2df79c055275c21749a1"
+SRC_URI[sha256sum] = "c1923b6bd166e6dd07be860c15f59e8273aaa8692bc2a1fce1d31b826b9b3fbe"
SRC_URI_append_de0-nano-soc = " \
file://0001-ARM-dts-socfpga-Rename-socfpga_cyclone5_de0_-sockit-.patch"
--
2.16.4
next prev parent reply other threads:[~2019-12-10 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 18:22 [PATCH v5 0/5] linux-custom recipe rework Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 1/5] recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs Jan Kiszka
2019-12-10 18:22 ` [PATCH v5 2/5] linux-mainline: fix stripping of .0 from the kernel version Jan Kiszka
2019-12-10 18:22 ` Jan Kiszka [this message]
2019-12-10 18:22 ` [PATCH v5 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb Jan Kiszka
2019-12-11 14:40 ` Jan Kiszka
2019-12-11 15:20 ` Gylstorff Quirin
2019-12-11 15:43 ` Jan Kiszka
2019-12-11 18:36 ` Jan Kiszka
2019-12-11 22:09 ` Henning Schild
2019-12-12 7:57 ` Gylstorff Quirin
2019-12-12 8:01 ` Jan Kiszka
2019-12-12 9:46 ` Gylstorff Quirin
2019-12-12 10:10 ` Gylstorff Quirin
2019-12-10 18:22 ` [PATCH v5 5/5] linux-mainline: Test config fragments Jan Kiszka
2019-12-19 15:19 ` [PATCH v5 0/5] linux-custom recipe rework cedric_hombourger
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=645fd80af21adcf3983a1a9ed24746557727c4e7.1576002128.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox