From: Alexander Smirnov <asmirnov@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v4] meta-isar: Rework boot files copying
Date: Thu, 19 Oct 2017 22:39:53 +0300 [thread overview]
Message-ID: <f32e0a54-d35d-1e45-f78e-afa0ec81ebd3@ilbers.de> (raw)
In-Reply-To: <20171019191357.11594-1-asmirnov@ilbers.de>
> 8<--
> Changes since v3:
> - Restored KERNEL_IMAGE and INITRD_IMAGE variables to support wic
> images creation.
> 8<--
>
> Currently there are two variables that contains hardcoded filenames
> with versions for kernel and initrd images. Isar uses them to copy these
> files to deploy directory. Moreover this is performed in ext4 class,
> what is logically wrong.
>
> This patch implements a new way which doesn't rely on hardcoded versioned
> filenames. Also it drops this copying from ext4 class.
>
> Signed-off-by: Frank Lenormand <lenormf@gmail.com>
> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>
Applied to next to start CI build. Will rework it if some issue will be
found.
next prev parent reply other threads:[~2017-10-19 19:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 19:23 [URGENT][PATCH v2 0/2] Correctly determine kernel and initrd versions Alexander Smirnov
2017-10-17 19:23 ` [URGENT][PATCH v2 1/2] meta-isar: Drop hardcoded kernel versions Alexander Smirnov
2017-10-17 19:23 ` [URGENT][PATCH v2 2/2] meta-isar: Rework boot files copying Alexander Smirnov
2017-10-18 14:06 ` [URGENT][PATCH v2 0/2] Correctly determine kernel and initrd versions Henning Schild
2017-10-19 16:00 ` Henning Schild
2017-10-19 16:08 ` Henning Schild
2017-10-19 19:18 ` Alexander Smirnov
2017-10-19 19:13 ` [PATCH v4] meta-isar: Rework boot files copying Alexander Smirnov
2017-10-19 19:39 ` Alexander Smirnov [this message]
2017-10-20 16:11 ` 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=f32e0a54-d35d-1e45-f78e-afa0ec81ebd3@ilbers.de \
--to=asmirnov@ilbers.de \
--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