linux-kernel - Re: [uclinux-dist-devel] [GIT PULL] Blackfin updates for 3.12

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+55aFwkKBbvN5sE5SxLpjZhUPE252s-3ptwnJ=9t97j_XAiAw@mail.gmail.com>
Date:	Mon, 16 Sep 2013 15:44:33 -0400
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Sonic Zhang <sonic.adi@...il.com>
Cc:	Steven Miao <realmz6@...nel.org>,
	adi-buildroot-devel@...ts.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [uclinux-dist-devel] [GIT PULL] Blackfin updates for 3.12

On Mon, Sep 16, 2013 at 1:28 AM, Sonic Zhang <sonic.adi@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/