From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Ubinize: made UBI volume name and volume alignment configurable
Date: Mon, 5 Mar 2012 21:05:24 +0100 [thread overview]
Message-ID: <20120305210524.22346643@skate> (raw)
In-Reply-To: <1330974852-27696-1-git-send-email-rolandu@gmail.com>
Hello Roland,
Thanks, it looks good to me. One comment below.
Le Mon, 5 Mar 2012 21:14:12 +0200,
Roland Uuesoo <rolandu@gmail.com> a ?crit :
> +config BR2_TARGET_ROOTFS_UBI_VOL_ALIGNMENT
> + int "UBI volume alignment"
> + depends on BR2_TARGET_ROOTFS_UBI
> + default 1
> + help
> + Default volume alignment
Could you add a bit more detail on what this 'volume alignment'
parameter is useful for.
> define ROOTFS_UBI_CMD
> - cp fs/ubifs/ubinize.cfg . ;\
> + cp fs/ubifs/ubinize.cfg $(BUILD_DIR)/_ubinize.cfg ;\
> + echo "vol_name=$(BR2_TARGET_ROOTFS_UBI_VOL_NAME)" \
> + >> $(BUILD_DIR)/_ubinize.cfg ;\
> + echo "vol_alignment=$(BR2_TARGET_ROOTFS_UBI_VOL_ALIGNMENT)" \
> + >> $(BUILD_DIR)/_ubinize.cfg ; \
> echo "image=$$@fs" \
> - >> ./ubinize.cfg ;\
> - $(HOST_DIR)/usr/sbin/ubinize -o $$@ $(UBI_UBINIZE_OPTS)
> ubinize.cfg ;\
> - rm ubinize.cfg
> + >> $(BUILD_DIR)/_ubinize.cfg ;\
> + $(HOST_DIR)/usr/sbin/ubinize -o $$@ $(UBI_UBINIZE_OPTS)
> $(BUILD_DIR)/_ubinize.cfg ;\
> + rm $(BUILD_DIR)/_ubinize.cfg
The indentation is a bit funky here. Can you keep the indentation at
one tab?
Thanks for your work!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-05 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 19:14 [Buildroot] [PATCH] Ubinize: made UBI volume name and volume alignment configurable Roland Uuesoo
2012-03-05 20:05 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 10:47 Roland Uuesoo
2012-03-11 13:22 ` Arnout Vandecappelle
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=20120305210524.22346643@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox