public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7: copy most options from tegra_defconfig
Date: Fri, 20 Dec 2013 13:26:17 -0700	[thread overview]
Message-ID: <52B4A7E9.9090900@wwwdotorg.org> (raw)
In-Reply-To: <CAOesGMh4PkdTh8EP1WS9-_5cVe1NWuNQPbkskk7hJhtbBEPWBg@mail.gmail.com>

On 12/20/2013 01:16 PM, Olof Johansson wrote:
> On Fri, Dec 20, 2013 at 12:04 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:

>> +CONFIG_EXT2_FS=y
>> +CONFIG_EXT2_FS_XATTR=y
>> +CONFIG_EXT2_FS_POSIX_ACL=y
>> +CONFIG_EXT2_FS_SECURITY=y
>> +CONFIG_EXT3_FS=y
>> +CONFIG_EXT3_FS_POSIX_ACL=y
>> +CONFIG_EXT3_FS_SECURITY=y
> 
> I think it makes sense to just enable EXT4_USE_FOR_EXT23 instead.

It looks like that's the default if EXT2_FS/EXT3_FS aren't enabled. I'll
go test that out.

>>  CONFIG_EXT4_FS=y
>> +CONFIG_VFAT_FS=y
>>  CONFIG_TMPFS=y
>> +CONFIG_SQUASHFS=y
>> +CONFIG_SQUASHFS_LZO=y
>> +CONFIG_SQUASHFS_XZ=y
>>  CONFIG_NFS_FS=y
>>  CONFIG_NFS_V3_ACL=y
>>  CONFIG_NFS_V4=y
>>  CONFIG_ROOT_NFS=y
>>  CONFIG_PRINTK_TIME=y
>>  CONFIG_DEBUG_FS=y
>> -CONFIG_DEBUG_KERNEL=y
> 
> Why are you disabling DEBUG_KERNEL?

It's not disabled, it ends up getting selected by something else, so
doesn't appear in the defconfig.

  reply	other threads:[~2013-12-20 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 20:04 [PATCH] ARM: multi_v7: copy most options from tegra_defconfig Stephen Warren
2013-12-20 20:16 ` Olof Johansson
2013-12-20 20:26   ` Stephen Warren [this message]
2013-12-22 20:05     ` Olof Johansson
2013-12-23 17:37       ` Olof Johansson
2014-01-24  0:16         ` Stephen Warren
2014-01-24  0:20           ` Olof Johansson
2014-01-24  0:21             ` Olof Johansson

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=52B4A7E9.9090900@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox