From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 2/5] v7a: images: remove redundant size specifications
Date: Mon, 26 Apr 2021 08:35:26 +0200 [thread overview]
Message-ID: <20210426063526.mun7ad7e7fpxkxf5@pengutronix.de> (raw)
In-Reply-To: <20210426060526.32029-2-rhi@pengutronix.de>
On Mon, Apr 26, 2021 at 08:05:23AM +0200, Roland Hieber wrote:
> For partitions that are filled by another image, it does not make sense
> to make partitions larger or smaller than their containing file system.
> In those cases, genimage can already determine the partition sizes from
> the referenced images, and calculates the partition offsets accordingly,
> so in most cases we don't have to keep track of the sizes at all.
>
> (A special case is vexpress.hdimg, which needs to have an empty block at
> the end as a workaround for qemu, in which case it is clearer to have
> all partition sizes and offsets explicitely in the config file. So don't
> touch vexpress.hdimg here.)
>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> configs/platform-v7a/config/images/at91-sd.config | 2 --
> configs/platform-v7a/config/images/beaglebone.config | 2 --
> configs/platform-v7a/config/images/gf.config | 2 --
> configs/platform-v7a/config/images/riotboard.config | 1 -
> configs/platform-v7a/config/images/rpi2.config | 2 --
> configs/platform-v7a/config/images/rpi3.config | 2 --
> configs/platform-v7a/config/images/rpicm3.config | 2 --
> configs/platform-v7a/config/images/sabrelite.config | 1 -
> configs/platform-v7a/config/images/stm32mp.config | 1 -
> configs/platform-v7a/config/images/udoo-neo.config | 1 -
> 10 files changed, 16 deletions(-)
Applied to next.
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2021-04-26 6:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 6:05 [DistroKit] [PATCH 1/5] v7a: image-vexpress: convert hex numbers to human-readable sizes Roland Hieber
2021-04-26 6:05 ` [DistroKit] [PATCH 2/5] v7a: images: remove redundant size specifications Roland Hieber
2021-04-26 6:35 ` Robert Schwebel [this message]
2021-04-26 6:05 ` [DistroKit] [PATCH 3/5] v7a: barebox: clean up defaultenvs Roland Hieber
2021-04-26 6:36 ` Robert Schwebel
2021-04-26 6:05 ` [DistroKit] [PATCH 4/5] v7a: run: remove telnet port forwarding Roland Hieber
2021-04-26 6:36 ` Robert Schwebel
2021-04-26 6:05 ` [DistroKit] [PATCH 5/5] v7a: run: randomise the SSH forwarding port Roland Hieber
2021-04-26 6:33 ` Michael Olbrich
2021-04-26 8:30 ` Roland Hieber
2021-04-26 8:35 ` [DistroKit] [PATCH v2] " Roland Hieber
2021-04-26 9:02 ` Robert Schwebel
2021-04-26 9:03 ` Robert Schwebel
2021-04-26 10:07 ` [DistroKit] [PATCH v3] v7a: run: make the SSH forwarding port multiprocess-compatible Roland Hieber
2021-04-26 10:09 ` Robert Schwebel
2021-04-26 6:35 ` [DistroKit] [PATCH 1/5] v7a: image-vexpress: convert hex numbers to human-readable sizes Robert Schwebel
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=20210426063526.mun7ad7e7fpxkxf5@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=rhi@pengutronix.de \
/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