Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753000AbcLFTEd (ORCPT ); Tue, 6 Dec 2016 14:04:33 -0500 Received: from mail-qt0-f193.google.com ([209.85.216.193]:34163 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751636AbcLFTE3 (ORCPT ); Tue, 6 Dec 2016 14:04:29 -0500 MIME-Version: 1.0 X-Originating-IP: [209.133.79.5] In-Reply-To: <1481027938-31831-1-git-send-email-b.zolnierkie@samsung.com> References: <1481027938-31831-1-git-send-email-b.zolnierkie@samsung.com> From: Olof Johansson Date: Tue, 6 Dec 2016 11:03:34 -0800 Message-ID: Subject: Re: [RFC PATCH 00/23] arm: defconfigs: use kconfig fragments To: Bartlomiej Zolnierkiewicz Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Russell King 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: 605 Lines: 22 On Tue, Dec 6, 2016 at 4:38 AM, Bartlomiej Zolnierkiewicz wrote: > Hi, > > This RFC patchset starts convertion of ARM defconfigs to use kconfig > fragments and dynamically generate defconfigs. The goals of this > work are to: You don't provide any motivation as to why this is better. As far as I am concerned it'll just be a mess. So: Nack. So much nack. I really don't want to see a proliferation of config fragments like this. I had a feeling it was a bad idea to pick up that one line config fragment before, since it opened the door for this kind of mess. :( -Olof