From: daggs <daggs@gmx.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] odroidc2: use first boot fs resize pkg.
Date: Fri, 23 Dec 2016 14:43:41 +0100 [thread overview]
Message-ID: <trinity-82c86be7-f597-4daf-9eb8-69263b5bb315-1482500621030@3capp-mailcom-bs05> (raw)
In-Reply-To: <20161217165123.1053e588@free-electrons.com>
Greetings,
> Hello,
>
> On Fri, 2 Dec 2016 12:10:28 +0200, Dagg Stompler wrote:
> > remove the hardcode limitation of the created rootfs parition size and
> > use the newly added first boot fs resize pkg to extend the fs to the max
> > possible.
> >
> > Signed-off-by: Dagg Stompler <daggs@gmx.com>
>
> I think we want to decide if we want to do this globally for all
> defconfig for which it makes sense. Having that just for one defconfig,
> but not all the other is a bit weird. Being consistent is quite
> important.
imho the first stage should be for the original board it was indented to, then extend it.
as I don't have other measures to test it, I didn't want to set it globally.
Dagg.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
next prev parent reply other threads:[~2016-12-23 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 10:10 [Buildroot] [PATCH 1/2] first_boot_rootfs_resizer: New Package Dagg Stompler
2016-12-02 10:10 ` [Buildroot] [PATCH 2/2] odroidc2: use first boot fs resize pkg Dagg Stompler
2016-12-17 15:51 ` Thomas Petazzoni
2016-12-23 13:43 ` daggs [this message]
2016-12-17 15:50 ` [Buildroot] [PATCH 1/2] first_boot_rootfs_resizer: New Package Thomas Petazzoni
2016-12-23 13:41 ` daggs
2016-12-23 14:00 ` Thomas Petazzoni
2016-12-23 19:08 ` daggs
2017-01-03 11:39 ` [Buildroot] [1/2] " Jérôme Pouiller
2017-02-25 10:54 ` daggs
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=trinity-82c86be7-f597-4daf-9eb8-69263b5bb315-1482500621030@3capp-mailcom-bs05 \
--to=daggs@gmx.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.