All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnab.basu@freescale.com (Arnab Basu)
To: linux-arm-kernel@lists.infradead.org
Subject: Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig
Date: Wed, 6 Aug 2014 00:16:47 +0530	[thread overview]
Message-ID: <53E12697.9090807@freescale.com> (raw)
In-Reply-To: <20140805134053.GJ18780@arm.com>

On 08/05/2014 07:10 PM, Will Deacon wrote:
> On Tue, Aug 05, 2014 at 02:26:42PM +0100, Arnab Basu wrote:
>> Hi
>
> Hi Arnab,
>
>> While trying to boot Linux with an initrd I found that
>> CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE are not part of the arm64
>> defconfig. Is this because no one has got around to adding them or is
>> this something that has been omitted on purpose?
>
> Do we really want CONFIG_BLK_DEV_RAM=y by default? The Kconfig text for the
> options says:
>
> 	Most normal users won't need the RAM disk functionality, and can
> 	thus say N here.
>
> so I'd be inclined to say we should leave things as they are. The current
> defconfig is largely driven by our testing efforts, but I've been enabling
> other options that could benefit many people without hindering others (e.g.
> DEVTMPFS_MOUNT).
>

Thanks for explaining Will.

Arnab

> Will
>

  reply	other threads:[~2014-08-05 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 13:26 Regarding CONFIG_BLK_DEV_RAM and CONFIG_BLK_DEV_RAM_SIZE in arch/arm64/configs/defconfig Arnab Basu
2014-08-05 13:40 ` Will Deacon
2014-08-05 18:46   ` Arnab Basu [this message]
2014-08-05 14:08 ` Christopher Covington
2014-08-05 18:39   ` Arnab Basu
2014-08-05 20:17     ` Christopher Covington

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=53E12697.9090807@freescale.com \
    --to=arnab.basu@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.