From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 56870C84 for ; Thu, 13 Sep 2018 11:41:29 +0000 (UTC) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DC4632C4 for ; Thu, 13 Sep 2018 11:41:28 +0000 (UTC) Received: by mail-io1-f47.google.com with SMTP id q5-v6so2857628iop.3 for ; Thu, 13 Sep 2018 04:41:28 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180913112738.GA8411@sirena.org.uk> References: <20180912185949.GC25894@wrath> <20180913112738.GA8411@sirena.org.uk> From: Daniel Vetter Date: Thu, 13 Sep 2018 13:41:26 +0200 Message-ID: To: Mark Brown Content-Type: text/plain; charset="UTF-8" Cc: Andy Shevchenko , ksummit Subject: Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Sep 13, 2018 at 1:27 PM, Mark Brown wrote: > On Wed, Sep 12, 2018 at 10:05:19PM +0200, Daniel Vetter wrote: >> On Wed, Sep 12, 2018 at 8:59 PM, Darren Hart wrote: > >> > Regarding tooling, Andy and I have documented our process and shared our >> > tooling which has evolved to try and prevent human error. I believe DRM >> > has something even more evolved. > >> > https://github.com/dvhart/pdx86-tools > >> Hm, the gen-config scrips looks like a really neat idea. Atm we >> manually maintain some configs for all the drm drivers, but this is >> much better I think. Next step up would be to double-check that make > > Yes, I've got a script like that as well (mine's a *tiny* bit less > sophisticated) - it's super handy if you frequently add new drivers. > >> Bit of googling and fooling around says make CONFIG_FOO=y olddefconfig >> seems to do this, including enabling (all?) dependencies you need. > > That only works for dependencies that are selected, if there's a config > option that stops CONFIG_FOO being seen by the user (eg, having MFD_FOO > preventing SUBSYSTEM_FOO being enabled) then it'll just get silently > ignored. I guess I fumbled something with my testing, this does indeed not work like I hoped :-/ -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch