From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/ext2: add options for extra space and extra inodes
Date: Thu, 29 Oct 2015 19:17:52 +0100 [thread overview]
Message-ID: <20151029181752.GA3600@free.fr> (raw)
In-Reply-To: <CAFGQKxcNOhG6TnWALz5BPqePSZFhchWQpwcVmbzCV10DTqPWqg@mail.gmail.com>
Martin, All,
On 2015-10-29 10:45 +0000, Martin Bark spake thusly:
> On 28 October 2015 at 23:06, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Add two options to the ext2 filesystem, one to add extra free space, one
> > to add extra free inodes.
> >
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> > ---
> > fs/ext2/Config.in | 20 ++++++++++++++++++--
> > fs/ext2/ext2.mk | 2 ++
> > package/mke2img/mke2img | 8 +++++++-
> > 3 files changed, 27 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/ext2/Config.in b/fs/ext2/Config.in
> > index 5b1cd0c..fb06cdd 100644
> > --- a/fs/ext2/Config.in
> > +++ b/fs/ext2/Config.in
> > @@ -45,13 +45,29 @@ config BR2_TARGET_ROOTFS_EXT2_LABEL
> > string "filesystem label"
> >
> > config BR2_TARGET_ROOTFS_EXT2_BLOCKS
> > - int "size in blocks (leave at 0 for auto calculation)"
> > + int "exact size in blocks (leave at 0 for auto calculation)"
> > default 0
> >
> > config BR2_TARGET_ROOTFS_EXT2_INODES
> > - int "inodes (leave at 0 for auto calculation)"
> > + int "exact number of inodes (leave at 0 for auto calculation)"
> > default 0
> >
> > +config BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS
> > + int "extra size in blocks" if BR2_TARGET_ROOTFS_EXT2_BLOCKS = 0
> > + default 0
> > + help
> > + Enter here the nmuber of extra blocks of free space you
>
> should be number not nmuber.
Damn keyboard dislexia! :-)
> > + want on your filesystem. By default, Buildroot will not
> > + leave much space free.
> > +
> > +config BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES
> > + int "extra inodes" if BR2_TARGET_ROOTFS_EXT2_INODES = 0
> > + default 0
> > + help
> > + Enter here the nmuber of extra free inodes you want on
>
> Same again
Thanks! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-10-29 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 23:06 [Buildroot] [PATCH] fs/ext2: add options for extra space and extra inodes Yann E. MORIN
2015-10-29 10:45 ` Martin Bark
2015-10-29 18:17 ` Yann E. MORIN [this message]
2015-10-29 18:18 ` Gustavo Zacarias
2015-10-30 11:01 ` Arnout Vandecappelle
2015-10-30 12:35 ` Yann E. MORIN
2015-10-30 12:54 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2015-10-29 9:00 [Buildroot] [PATCH v3 0/2] Alternative way to wait interfaces on bootup Jérôme Pouiller
2015-10-29 9:00 ` [Buildroot] [PATCH v3 2/2] skeleton: optionally wait for network interfaces to appear Jérôme Pouiller
2015-10-29 20:26 ` [Buildroot] [PATCH] fs/ext2: add options for extra space and extra inodes Yann E. MORIN
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=20151029181752.GA3600@free.fr \
--to=yann.morin.1998@free.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox