From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/1] Refactor ext4 image class
Date: Wed, 27 Feb 2019 10:28:08 +0100 [thread overview]
Message-ID: <75601c6c-fd2f-ae99-7512-90e2145b1af6@ilbers.de> (raw)
In-Reply-To: <20190218130429.9881-1-claudius.heine.ext@siemens.com>
Hi Claudius,
I would prefer to avoid dropping support for jessie (at least for
upcoming release).
Regards,
Maxim.
On 2/18/19 2:04 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> this patchset brings the ext4 image up to date to how the other images
> are created.
>
> This depends on 'mkfs.ext4 -d' parameter beeing available on the host,
> so there is no support for jessie, where this is not available.
>
> regards,
> Claudius
>
> Claudius Heine (1):
> meta/ext4-img: refactor to fit current image creation methods
>
> meta-isar/classes/rpi-sdimg.bbclass | 2 +-
> meta/classes/ext4-img.bbclass | 31 +++++++++++------------------
> 2 files changed, 13 insertions(+), 20 deletions(-)
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2019-02-27 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 13:04 claudius.heine.ext
2019-02-18 13:04 ` [PATCH 1/1] meta/ext4-img: refactor to fit current image creation methods claudius.heine.ext
2019-02-19 9:25 ` Henning Schild
2019-02-26 11:35 ` cedric_hombourger
2019-02-26 11:56 ` Jan Kiszka
2019-02-26 12:12 ` Henning Schild
2019-02-26 12:24 ` Hombourger, Cedric
2019-03-28 9:58 ` Maxim Yu. Osipov
2019-03-28 12:02 ` Hombourger, Cedric
2019-03-29 7:55 ` Adler, Michael
2019-03-29 8:45 ` Maxim Yu. Osipov
2019-02-27 9:28 ` Maxim Yu. Osipov [this message]
2019-03-28 12:40 ` [PATCH 0/1] Refactor ext4 image class Maxim Yu. Osipov
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=75601c6c-fd2f-ae99-7512-90e2145b1af6@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@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