From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 0/4] Version updates, snapshot-based RISC-V
Date: Tue, 5 Mar 2024 10:07:29 +0100 [thread overview]
Message-ID: <cover.1709629653.git.jan.kiszka@siemens.com> (raw)
See patches for details.
Jan
Jan Kiszka (4):
linux-cip: Update to 4.19.306-cip107-rt35 and 6.1.80-cip16[-rt9]
Switch sid-based riscv64 back to a snapshot
Update Isar to release 0.10
linux-cip: Update cip-kernel-config
conf/distro/cip-core-sid.conf | 3 +++
conf/distro/cip-debian-sid-snapshot.list | 2 ++
kas-cip.yml | 2 +-
recipes-kernel/linux/cip-kernel-config.inc | 4 ++--
...99-cip105-rt34.bb => linux-cip-rt_4.19.306-cip107-rt35.bb} | 2 +-
...t_6.1.75-cip14-rt8.bb => linux-cip-rt_6.1.80-cip16-rt9.bb} | 2 +-
.../{linux-cip_6.1.75-cip14.bb => linux-cip_6.1.80-cip16.bb} | 2 +-
7 files changed, 11 insertions(+), 6 deletions(-)
create mode 100644 conf/distro/cip-debian-sid-snapshot.list
rename recipes-kernel/linux/{linux-cip-rt_4.19.299-cip105-rt34.bb => linux-cip-rt_4.19.306-cip107-rt35.bb} (68%)
rename recipes-kernel/linux/{linux-cip-rt_6.1.75-cip14-rt8.bb => linux-cip-rt_6.1.80-cip16-rt9.bb} (59%)
rename recipes-kernel/linux/{linux-cip_6.1.75-cip14.bb => linux-cip_6.1.80-cip16.bb} (59%)
--
2.35.3
next reply other threads:[~2024-03-05 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 9:07 Jan Kiszka [this message]
2024-03-05 9:07 ` [isar-cip-core][PATCH 1/4] linux-cip: Update to 4.19.306-cip107-rt35 and 6.1.80-cip16[-rt9] Jan Kiszka
2024-03-05 9:07 ` [isar-cip-core][PATCH 2/4] Switch sid-based riscv64 back to a snapshot Jan Kiszka
2024-03-05 9:07 ` [isar-cip-core][PATCH 3/4] Update Isar to release 0.10 Jan Kiszka
2024-03-05 9:07 ` [isar-cip-core][PATCH 4/4] linux-cip: Update cip-kernel-config Jan Kiszka
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=cover.1709629653.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.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