Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751339Ab3IPToh (ORCPT ); Mon, 16 Sep 2013 15:44:37 -0400 Received: from mail-ve0-f170.google.com ([209.85.128.170]:44363 "EHLO mail-ve0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750799Ab3IPToe (ORCPT ); Mon, 16 Sep 2013 15:44:34 -0400 MIME-Version: 1.0 In-Reply-To: References: <1379049145-16017-1-git-send-email-realmz6@kernel.org> Date: Mon, 16 Sep 2013 15:44:33 -0400 X-Google-Sender-Auth: 1a4m2CuLocxzzCpvXJ-yYLvsevs Message-ID: Subject: Re: [uclinux-dist-devel] [GIT PULL] Blackfin updates for 3.12 From: Linus Torvalds To: Sonic Zhang Cc: Steven Miao , adi-buildroot-devel@lists.sourceforge.net, Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1101 Lines: 24 On Mon, Sep 16, 2013 at 1:28 AM, Sonic Zhang wrote: > > I am sorry to put many config options into the Blackfin Kconfig file. > In the case this is not preferred, we will make sure no more device > config options are put into the Kconfig files. It's not so much "no more device config options", it's more a matter of level. If it's a couple of core options in the SoC, what the heck, use Kconfig. Many of your board files are pretty small and have one or two device config options in them. That's fine. It's when it's thousands of lines of Kconfig file (and that isn't even comments or anything like that), then that's a sign that you should start seriously thinking about using some proper device configuration. Device-tree is the one most architectures use, but heck, maybe it's overkill for blackfin. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/