From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 31AD2EB64DA for ; Tue, 4 Jul 2023 07:18:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229647AbjGDHSA (ORCPT ); Tue, 4 Jul 2023 03:18:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43402 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231322AbjGDHRy (ORCPT ); Tue, 4 Jul 2023 03:17:54 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 805961A2; Tue, 4 Jul 2023 00:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1688455070; x=1719991070; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=E5NBCKClhK46jwcevA3AhRLGaK+1QlR+RReRt1xL4Mo=; b=g3kWCbfa8nFH3NMXV6AFjPRLQOAaELDbaEzmApZRYLkChO8QVElZ1HQ5 x77JR4OWNesOwqXjth2BIM6cCTj+LwE1cG++/epIQMMRlTBG9UhHTnDxE G2IgJYRUAROWWHkIQ+p3nkZFo7EDfkvx8256OOMgpkYD2HowROls72JKm VcknwniwBq0kCkwoo0C6KWOwLkdyjAYZCnIcZLFP1JgiVOMi2nnigVvF0 piZ3Z+UuUh088n+TfaRteMNtO+qv66sJNs5F44mlmkFFztU5lMfFlwANn peF+pkIHu3T1CIbJfEylM34AMAGdyc3Vlr12Dcc7DzbIY0DLRkzavtyWF A==; X-IronPort-AV: E=McAfee;i="6600,9927,10760"; a="342646999" X-IronPort-AV: E=Sophos;i="6.01,179,1684825200"; d="scan'208";a="342646999" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jul 2023 00:17:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10760"; a="842900336" X-IronPort-AV: E=Sophos;i="6.01,179,1684825200"; d="scan'208";a="842900336" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP; 04 Jul 2023 00:17:46 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1qGaIC-0024DD-2J; Tue, 04 Jul 2023 10:17:44 +0300 Date: Tue, 4 Jul 2023 10:17:44 +0300 From: Andy Shevchenko To: Javier Martinez Canillas Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven , Thomas Zimmermann , Arnd Bergmann , Daniel Vetter , Helge Deller , Randy Dunlap , Sam Ravnborg , dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org Subject: Re: [PATCH v4 2/5] fbdev: Move core fbdev symbols to a separate Kconfig file Message-ID: References: <20230703230534.997525-1-javierm@redhat.com> <20230703230534.997525-3-javierm@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230703230534.997525-3-javierm@redhat.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-fbdev@vger.kernel.org On Tue, Jul 04, 2023 at 01:05:26AM +0200, Javier Martinez Canillas wrote: > The drivers/video/fbdev/Kconfig defines both symbols for fbdev drivers and > core fbdev symbols, that can be enabled independently of the fbdev drivers. > > Split the Kconfig in two, one that only has the symbols for fbdev drivers > and another one that contains the fbdev core symbols. ... > source "drivers/video/fbdev/omap/Kconfig" > source "drivers/video/fbdev/omap2/Kconfig" > source "drivers/video/fbdev/mmp/Kconfig" > + > +source "drivers/video/fbdev/core/Kconfig" Hmm... Shan't we start Kconfig from core options? -- With Best Regards, Andy Shevchenko