From: Mark Jackson <mpfj-list@newflow.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs/ubifs: factorize all the "depends on" into "if...endif" blocks
Date: Thu, 25 Apr 2013 08:49:52 +0100 [thread overview]
Message-ID: <5178E020.4050605@newflow.co.uk> (raw)
In-Reply-To: <20130424212620.GC24710@free.fr>
On 24/04/13 22:26, Yann E. MORIN wrote:
> Mark, All,
>
> On Wed, Apr 24, 2013 at 01:30:25PM +0100, Mark Jackson wrote:
>> All the UBIFS options use "depends on BR2_TARGET_ROOTFS_UBIFS" but
>> we can simplify the config file by enclosing them in an "if..endif"
>> block.
>>
>> We also do the same for the "depends on BR2_TARGET_ROOTFS_UBI".
>
> A few comments below (mostly nitpicking, but hey! ;-) )
>
>> Signed-off-by: Mark Jackson <mpfj@newflow.co.uk>
>> ---
>> fs/ubifs/Config.in | 18 ++++++++----------
>> 1 file changed, 8 insertions(+), 10 deletions(-)
>>
>> diff --git a/fs/ubifs/Config.in b/fs/ubifs/Config.in
>> index f17c7dc..c1d2ce7 100644
>> --- a/fs/ubifs/Config.in
>> +++ b/fs/ubifs/Config.in
>> @@ -3,21 +3,20 @@ config BR2_TARGET_ROOTFS_UBIFS
>> help
>> Build a ubifs root filesystem
>>
>> +if BR2_TARGET_ROOTFS_UBIFS
> [--SNIP--]
>> +if BR2_TARGET_ROOTFS_UBI
> [--SNIP--]
>> +endif
>> +
>> +endif
>
> Comment the endif-s so we know at a glance to which if they belong to:
>
> +endif # BR2_TARGET_ROOTFS_UBI
> +
> +endif # BR2_TARGET_ROOTFS_UBIFS
I *very* nearly put those in anyway, but checked with a few other Config.in files
and none of them had such closing comments.
> With that fixed:
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
I'll post a v2.
Cheers
Mark J.
next prev parent reply other threads:[~2013-04-25 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 12:30 [Buildroot] [PATCH] fs/ubifs: factorize all the "depends on" into "if...endif" blocks Mark Jackson
2013-04-24 21:26 ` Yann E. MORIN
2013-04-25 2:23 ` Thomas Petazzoni
2013-04-25 7:49 ` Mark Jackson [this message]
2013-04-25 8:06 ` 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=5178E020.4050605@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--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