Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9] fs/ext2: cleanups and improvements
Date: Mon, 1 May 2017 22:58:21 +0200	[thread overview]
Message-ID: <20170501205821.GE3118@scaer> (raw)
In-Reply-To: <20170501211852.6193ab52@free-electrons.com>

Thomas, All,

On 2017-05-01 21:18 +0200, Thomas Petazzoni spake thusly:
> On Mon,  1 May 2017 17:58:39 +0200, Yann E. MORIN wrote:
> > J Evans (1):
> >       ext2: add help text for BR2_TARGET_ROOTFS_EXT2_BLOCKS
> > 
> > Yann E. MORIN (8):
> >       package/mke2img: check nb_blocks is specified
> >       package/mke2img: specifying zero inodes means auto
> >       fs/ext2: always pass the number of inodes
> >       fs/ext2: always pass the label option
> >       fs/ext2: allow reserving zero block for root
> >       fs/ext2: simplify code
> >       package/mke2img: add option to specify block size
> >       fs/ext2: add option to specify block size
> 
> In general, I find this good. However, it badly conflicts with the
> on-going work to move away from mke2img/genext2fs and use mkfs.ext2/3/4
> instead.

But this is not ready yet, is it?

> For example, I believe mkfs.ext2/3/4 will automatically chose a sane
> default block size depending on the filesystem size.

And even if it does, ther are stil cases where one wants to override the
auto-calculated size.

So, even when we switch the backend that generates the filesystem, we'd
still want to have those options, I believe.

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.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2017-05-01 20:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 15:58 [Buildroot] [PATCH 0/9] fs/ext2: cleanups and improvements Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 1/9] ext2: add help text for BR2_TARGET_ROOTFS_EXT2_BLOCKS Yann E. MORIN
2017-05-04 15:15   ` Thomas Petazzoni
2017-05-01 15:58 ` [Buildroot] [PATCH 2/9] package/mke2img: check nb_blocks is specified Yann E. MORIN
2017-05-13 13:17   ` Thomas Petazzoni
2017-05-01 15:58 ` [Buildroot] [PATCH 3/9] package/mke2img: specifying zero inodes means auto Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 4/9] fs/ext2: always pass the number of inodes Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 5/9] fs/ext2: always pass the label option Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 6/9] fs/ext2: allow reserving zero block for root Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 7/9] fs/ext2: simplify code Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 8/9] package/mke2img: add option to specify block size Yann E. MORIN
2017-05-01 15:58 ` [Buildroot] [PATCH 9/9] fs/ext2: " Yann E. MORIN
2017-05-01 19:18 ` [Buildroot] [PATCH 0/9] fs/ext2: cleanups and improvements Thomas Petazzoni
2017-05-01 20:58   ` Yann E. MORIN [this message]

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=20170501205821.GE3118@scaer \
    --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