From: Henning Schild <henning.schild@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com" <claudius.heine.ext@siemens.com>
Cc: <isar-users@googlegroups.com>, Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v2 1/4] doc/user: added targz-img to image type list
Date: Wed, 30 Jan 2019 17:19:23 +0100 [thread overview]
Message-ID: <20190130171923.0fdcf716@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20190130080229.604-2-claudius.heine.ext@siemens.com>
If there will be more iterations, i guess this simple one should go
stand-alone.
Henning
On Wed, 30 Jan 2019 09:02:26 +0100
"[ext] claudius.heine.ext@siemens.com" <claudius.heine.ext@siemens.com>
wrote:
> From: Claudius Heine <ch@denx.de>
>
> Signed-off-by: Claudius Heine <ch@denx.de>
> ---
> doc/user_manual.md | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index eebcaa9..c4fe42a 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -471,10 +471,11 @@ IMAGE_TYPE = "my-image"
>
> ### Reference Classes
>
> -Isar contains three image type classes that can be used as reference:
> +Isar contains additional image type classes that can be used as
> reference:
> - `ext4-img`
> - `rpi-sdimg`
> + - `targz-img`
> - `wic-img`
>
> ---
next prev parent reply other threads:[~2019-01-30 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 8:02 [PATCH v2 0/4] UBI support claudius.heine.ext
2019-01-30 8:02 ` [PATCH v2 1/4] doc/user: added targz-img to image type list claudius.heine.ext
2019-01-30 16:19 ` Henning Schild [this message]
2019-01-30 8:02 ` [PATCH v2 2/4] meta/classes: added ubifs-img class claudius.heine.ext
2019-01-30 8:02 ` [PATCH v2 3/4] meta/classes: added ubi-img class claudius.heine.ext
2019-01-30 8:02 ` [PATCH v2 4/4] meta-isar: added nand-ubi-demo example to demonstrate UBI use claudius.heine.ext
2019-01-30 16:32 ` Henning Schild
2019-01-31 10:11 ` Claudius Heine
2019-01-30 12:57 ` [PATCH v2 0/4] UBI support Claudius Heine
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=20190130171923.0fdcf716@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--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