From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752495AbdK0O1a (ORCPT ); Mon, 27 Nov 2017 09:27:30 -0500 Received: from mail-ot0-f194.google.com ([74.125.82.194]:39474 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752224AbdK0O10 (ORCPT ); Mon, 27 Nov 2017 09:27:26 -0500 X-Google-Smtp-Source: AGs4zMaSc/NWEeudoa2NlSzP9hveFirUTl0ipReEHKNxARGkJ278HnvTu3peulm+9URMTm2Dxy/QBW2VSXhAcZCf8Cw= MIME-Version: 1.0 In-Reply-To: References: From: Arnd Bergmann Date: Mon, 27 Nov 2017 15:27:24 +0100 X-Google-Sender-Auth: lpAbQIATDrJ479sdTJB-cvgjc6I Message-ID: Subject: Re: [PATCH v2 24/35] nds32: defconfig To: Greentime Hu Cc: Greentime , Linux Kernel Mailing List , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , Networking , Vincent Chen , DTML , Al Viro , David Howells , Will Deacon , Daniel Lezcano , linux-serial@vger.kernel.org, Vincent Chen Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 27, 2017 at 1:28 PM, Greentime Hu wrote: > +CONFIG_EXPERT=y You normally shouldn't need CONFIG_EXPERT in a defconfig file, by definition this is needed for unusual configurations only. > +CONFIG_NDS32_BUILTIN_DTB="ae3xx" Having a built-in DTB also makes no sense for a defconfig, when the idea is that it can run on as many machines as possible. > +CONFIG_BLK_DEV_LOOP=y > +CONFIG_BLK_DEV_RAM=y > +CONFIG_BLK_DEV_RAM_SIZE=8192 Having ramdisk built-in is rather unusual, most users don't use ramdisks any more since we don't need it for booting with the initramfs. > +CONFIG_BRIDGE=y > +CONFIG_TUN=y These also look unusual. Would it make sense to have these as loadable modules, or do you require having everything built-in for your workflow? > +CONFIG_SOUND=y > +CONFIG_SND=y > +# CONFIG_SND_SUPPORT_OLD_API is not set > +# CONFIG_SND_VERBOSE_PROCFS is not set It seems the sound subsystem is enabled, but no drivers are selected, so it won't actually do anything. > +# CONFIG_USB_SUPPORT is not set > +CONFIG_MMC=y Same for MMC. If you are still trying to get the respective device drivers merged, that doesn't need to stop you from enabling the configurations here. Arnd