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 F16A5899 for ; Wed, 28 Jun 2017 00:14:27 +0000 (UTC) Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A9230A4 for ; Wed, 28 Jun 2017 00:14:27 +0000 (UTC) Received: by mail-it0-f41.google.com with SMTP id b205so25013040itg.1 for ; Tue, 27 Jun 2017 17:14:27 -0700 (PDT) MIME-Version: 1.0 Sender: linus971@gmail.com In-Reply-To: References: <20170627135839.GB1886@jagdpanzerIV.localdomain> <20170627184448.GU21846@wotan.suse.de> <20170627231011.GA10543@mail.hallyn.com> From: Linus Torvalds Date: Tue, 27 Jun 2017 17:14:26 -0700 Message-ID: To: "Luis R. Rodriguez" Content-Type: text/plain; charset="UTF-8" Cc: Cristina Moraru , ksummit Subject: Re: [Ksummit-discuss] [TECH TOPIC] is Kconfig a bit hard sometimes? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Jun 27, 2017 at 5:09 PM, Luis R. Rodriguez wrote: > > The *easier* thing to do for now was to just map a loaded module to a > kconfig symbol, and she proposed fairly simple patches to do this. Well, localmodconfig does that today already. And as mentioned, this is *not* even primarily about devices. Devices are actually the easy case. Not only are they generally fairly easy to enumerate (ie lsusb etc), they are things that people are at least more or less aware of. The config options that don't enable drivers, but enable particular behavior - *those* are actually the nastiest ones. And you don't see those in module names (well, you obviously sometimes do, since the module might be what implements the behavior, but quite often it's a built-in or just a setting for a module) Linus