Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754178AbbEMIoJ (ORCPT ); Wed, 13 May 2015 04:44:09 -0400 Received: from mail-oi0-f52.google.com ([209.85.218.52]:35877 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753790AbbEMIoG (ORCPT ); Wed, 13 May 2015 04:44:06 -0400 MIME-Version: 1.0 In-Reply-To: <20150512145749.GA2324@station.rsr.lip6.fr> References: <20150512145749.GA2324@station.rsr.lip6.fr> Date: Wed, 13 May 2015 10:44:06 +0200 Message-ID: Subject: Re: lpc18xx: undefined Kconfig option ARCH_LPC18XX From: Linus Walleij To: Valentin Rothberg Cc: Joachim Eastwood , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , Alexandre Courbot , Paul Bolle , hengelein Stefan , Andreas Ruprecht 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: 1471 Lines: 31 On Tue, May 12, 2015 at 4:57 PM, Valentin Rothberg wrote: > [Me]: >> The answer to whether a certain maintainer will dare to do so >> or not is per individual preference. The crucial point is that >> "time savings" trumps "nothing can ever go wrong". > > I understand your point completely. However, I see some cases critical, > especially when configuration conditional code is added that cannot be > compiled since the Kconfig option is not added yet or due to some other > reason. In precise, I see a conflict in the golden rule of "don't break > the build". As the code cannot be compiled, nobody knows if it's broken > or not. I see such things happening nearly daily. I would say it is based on individual trust. Some contributors do not send me untested patch sets so I know I can apply one or two of them in isolation and trust the end result to be good if they work like this. Individual trust is at odds with process. Process is based on the bureaucratic ambition to work predictably and impersonal, such as works the planets, or the plants. But maintainers in practice, while applying some process, eventually work by personal trust which is more ephemeral. Yours, Linus Walleij -- 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/