From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [URGENT PATCH] multiconfig: update stretch kernel versions
Date: Fri, 13 Oct 2017 13:20:16 +0200 [thread overview]
Message-ID: <0f46818f-6382-2eb4-1837-430a808d4876@siemens.com> (raw)
In-Reply-To: <20171013111827.14823-1-henning.schild@siemens.com>
On 2017-10-13 13:18, [ext] Henning Schild wrote:
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
Even without "urgent" in the topic, a reason in the commit log remains
mandatory.
Jan
> ---
> meta-isar/conf/multiconfig/qemuamd64-stretch.conf | 6 +++---
> meta-isar/conf/multiconfig/qemuarm-stretch.conf | 6 +++---
> meta-isar/conf/multiconfig/qemui386-stretch.conf | 6 +++---
> 3 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/meta-isar/conf/multiconfig/qemuamd64-stretch.conf b/meta-isar/conf/multiconfig/qemuamd64-stretch.conf
> index 9ae0f75..c2bf21c 100644
> --- a/meta-isar/conf/multiconfig/qemuamd64-stretch.conf
> +++ b/meta-isar/conf/multiconfig/qemuamd64-stretch.conf
> @@ -8,11 +8,11 @@ DISTRO_ARCH ?= "amd64"
>
> IMAGE_PREINSTALL += " \
> init \
> - linux-image-4.9.0-3-amd64 \
> + linux-image-4.9.0-4-amd64 \
> "
>
> -KERNEL_IMAGE ?= "vmlinuz-4.9.0-3-amd64"
> -INITRD_IMAGE ?= "initrd.img-4.9.0-3-amd64"
> +KERNEL_IMAGE ?= "vmlinuz-4.9.0-4-amd64"
> +INITRD_IMAGE ?= "initrd.img-4.9.0-4-amd64"
>
> ROOTFS_DEV ?= "sda"
>
> diff --git a/meta-isar/conf/multiconfig/qemuarm-stretch.conf b/meta-isar/conf/multiconfig/qemuarm-stretch.conf
> index e793f8f..8b55a2f 100644
> --- a/meta-isar/conf/multiconfig/qemuarm-stretch.conf
> +++ b/meta-isar/conf/multiconfig/qemuarm-stretch.conf
> @@ -8,11 +8,11 @@ DISTRO_ARCH ?= "armhf"
>
> IMAGE_PREINSTALL += " \
> init \
> - linux-image-4.9.0-3-armmp \
> + linux-image-4.9.0-4-armmp \
> "
>
> -KERNEL_IMAGE ?= "vmlinuz-4.9.0-3-armmp"
> -INITRD_IMAGE ?= "initrd.img-4.9.0-3-armmp"
> +KERNEL_IMAGE ?= "vmlinuz-4.9.0-4-armmp"
> +INITRD_IMAGE ?= "initrd.img-4.9.0-4-armmp"
>
> ROOTFS_DEV ?= "vda"
>
> diff --git a/meta-isar/conf/multiconfig/qemui386-stretch.conf b/meta-isar/conf/multiconfig/qemui386-stretch.conf
> index fa38120..7749bf2 100644
> --- a/meta-isar/conf/multiconfig/qemui386-stretch.conf
> +++ b/meta-isar/conf/multiconfig/qemui386-stretch.conf
> @@ -8,11 +8,11 @@ DISTRO_ARCH ?= "i386"
>
> IMAGE_PREINSTALL += " \
> init \
> - linux-image-4.9.0-3-686-pae \
> + linux-image-4.9.0-4-686-pae \
> "
>
> -KERNEL_IMAGE ?= "vmlinuz-4.9.0-3-686-pae"
> -INITRD_IMAGE ?= "initrd.img-4.9.0-3-686-pae"
> +KERNEL_IMAGE ?= "vmlinuz-4.9.0-4-686-pae"
> +INITRD_IMAGE ?= "initrd.img-4.9.0-4-686-pae"
>
> ROOTFS_DEV ?= "sda"
>
>
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2017-10-13 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 11:18 Henning Schild
2017-10-13 11:20 ` Jan Kiszka [this message]
2017-10-13 11:20 ` Henning Schild
2017-10-13 11:42 ` [URGENT PATCHv2] " Henning Schild
2017-10-13 14:37 ` Baurzhan Ismagulov
2017-10-13 15:54 ` [URGENT PATCH] " Jan Kiszka
2017-10-13 16:21 ` Baurzhan Ismagulov
2017-10-16 8:04 ` Henning Schild
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=0f46818f-6382-2eb4-1837-430a808d4876@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@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