Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: enable ubi and ubifs if we build a ubifs root filesystem
Date: Tue, 31 Jul 2012 21:48:23 +0200	[thread overview]
Message-ID: <20120731214823.6060b684@skate> (raw)
In-Reply-To: <1343721051-8380-1-git-send-email-fabio.porcedda@gmail.com>

Hello,

Thanks for proposing this patch!

Le Tue, 31 Jul 2012 09:50:51 +0200,
Fabio Porcedda <fabio.porcedda@gmail.com> a ?crit :

> +	$(if $(BR2_TARGET_ROOTFS_UBIFS),
> +		$(call KCONFIG_ENABLE_OPT,CONFIG_MTD_UBI,$(@D)/.config)
> +		$(call KCONFIG_ENABLE_OPT,CONFIG_UBIFS_FS,$(@D)/.config))

As Tzu-Jung said, the topic of automatically adjusting the kernel
configuration depending on other configuration options is a sensitive
topic. For example: should we enable Netfilter in the kernel if
iptables package is enabled? Should we enable the MTD subsystem in the
kernel if the mtd-utils package is enabled? Since we definitely don't
want to fiddle too much with the kernel configuration of the user, we
trying to limit the number of such automatic tweaks.

At the moment, I'm leaning towards not doing automatic modification of
the kernel configuration depending on the root filesystem type selected
in Buildroot. Let's keep this up to the user. But I'll listen to the
comments of the other developers/users.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2012-07-31 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  7:50 [Buildroot] [PATCH] linux: enable ubi and ubifs if we build a ubifs root filesystem Fabio Porcedda
2012-07-31  9:24 ` Tzu-Jung Lee
2012-07-31 19:48 ` Thomas Petazzoni [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=20120731214823.6060b684@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