Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp371708ybv; Wed, 19 Feb 2020 01:12:43 -0800 (PST) X-Google-Smtp-Source: APXvYqy3la1Fe3tT0Z1Mjcwjc6+qUX0n+Mj7lhX4jB6d4txUp3rBmyD2Kyw8sA1e4MtpMFli712S X-Received: by 2002:a9d:6d10:: with SMTP id o16mr19509118otp.28.1582103563217; Wed, 19 Feb 2020 01:12:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582103563; cv=none; d=google.com; s=arc-20160816; b=FU+IvDAMgamhjtCRhwHjJx8kWCxN6JH2MlaA7c6CShVKIkjcyO+mpdHWRsmeFBbUlh ZzlFww2DhW0XSjtfMBMlvPzgnQ8fzy/+ZYhASHyvJlLLc7H7RAQhcfTrqygOSHCx9c9n 81oUZb9CMbwW7zY8qZ7iwX+7CSvofk9tGdabGjTUX4mUzZ0jQDOyhgUelGRJyU5phDz/ 39foPn4ScOIG1Ai7BT9sDi+XIrTzyTWXv/ZoxFESU6lNHOSK1A7BWiKYiiuCULsyml0K P5hb10tUYKCoIB/KnB1CRq8ni1tzQzrzNS9z5rRdK8BxNlP3invATFJFymfMOZzHReWk tt9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ubCLCP7nGW5yRnesKmd83D+FOged488/rLWfwm7JWcc=; b=hkJDLYjJ5oVlGaKNz/rV3lO80X4YwQz4deDzij2ZUzzAWqHSIwciGdW6VI+2oQwBMV APd5ddvnOKqlmInAxRMVX4F/uv7Q9wIJxV7djbd65I8QSPMzGL5F2ZrBtdmnFdt07T1N OeW2rxhhjxPKWN988rs2D2lNX18P069iELRVAPFs7cQudPQPBjVJ6xlfjZUpqEdoYPGZ jucxor4sQ9oo4nUeHjoJ8hyu0lA2xRRadOq9AW1N1YBkcXZf5woslJtekFxHyiV/7EPv g5G7BGCB4YvUnKy1D6L8374xCIHvm4SBE7dnK+glmqnPkjsYHxI2zpgKQibCfSNNSzTJ fXBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=xbeSCwsb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p23si867504otk.119.2020.02.19.01.12.31; Wed, 19 Feb 2020 01:12:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=xbeSCwsb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726647AbgBSJLv (ORCPT + 99 others); Wed, 19 Feb 2020 04:11:51 -0500 Received: from mail.kernel.org ([198.145.29.99]:49488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726260AbgBSJLr (ORCPT ); Wed, 19 Feb 2020 04:11:47 -0500 Received: from dragon (80.251.214.228.16clouds.com [80.251.214.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5568E2465D; Wed, 19 Feb 2020 09:11:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582103506; bh=QCvgFW+jje9yRaAt1NfJVzEVNG0lPbPPQv2SFoSGdiQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=xbeSCwsbekmtynqP4aaaVxyYrIPZSG/r77Cu0pb57sc/W83msL+MuTXIdMD65wILM Lxjn733f1xxww5TnjaWMcn0AhixWbvJAezZ8p9tYu9uMrzKp2xhmJ4HHJblvgEK6d4 9/27hQJWnAZa+NPqoKTsBxaDjfrCu3pgmQk4Uye4= Date: Wed, 19 Feb 2020 17:11:39 +0800 From: Shawn Guo To: Christian Gmeiner Cc: Krzysztof Kozlowski , LKML , Russell King , Olof Johansson , Alexandre Torgue , Arnd Bergmann , Geert Uytterhoeven , Patrice Chotard , Joel Stanley , Tony Lindgren , Lubomir Rintel , Enric Balletbo i Serra , linux-arm-kernel@lists.infradead.org, Sascha Hauer , Fabio Estevam , Philipp Zabel Subject: Re: [PATCH] ARM: multi_v7_defconfig: enable drm imx support Message-ID: <20200219091138.GA12803@dragon> References: <20200124084359.16817-1-christian.gmeiner@gmail.com> <20200217041936.GH5395@dragon> <20200218091409.GA6075@dragon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 19, 2020 at 09:48:23AM +0100, Christian Gmeiner wrote: > Am Di., 18. Feb. 2020 um 10:14 Uhr schrieb Shawn Guo : > > > > On Mon, Feb 17, 2020 at 01:09:32PM +0100, Christian Gmeiner wrote: > > > Am Mo., 17. Feb. 2020 um 05:19 Uhr schrieb Shawn Guo : > > > > > > > > On Mon, Feb 10, 2020 at 02:30:12PM +0100, Christian Gmeiner wrote: > > > > > Am Mo., 10. Feb. 2020 um 11:58 Uhr schrieb Krzysztof Kozlowski > > > > > : > > > > > > > > > > > > On Mon, 10 Feb 2020 at 11:54, Christian Gmeiner > > > > > > wrote: > > > > > > > > > > > > > > Am Fr., 24. Jan. 2020 um 09:44 Uhr schrieb Christian Gmeiner > > > > > > > : > > > > > > > > > > > > > > > > Makes it possible to multi v7 defconfig for stm32 and imx based devices with > > > > > > > > What do you mean by stm32 based devices here? > > > > > > > > > > CONFIG_ARCH_STM32 - I have a STM32MP157C-DK2 in my board farm and > > > would love to use > > > multi_v7 for imx6 and stm32. > > > > The patch is all about enabling drm-imx driver support. The commit log > > gives the impression that drm-imx driver also works on stm32 devices. > > Is that the case? > > > > No - the common thing both share is etnaviv. I did not know that before, and thanks for the information. But looking at the code change, there is nothing about etnaviv driver, and it's all about drm-imx driver. So I'm still questioning why stm32 needs to be mentioned in the commit log at all. > The patch subject "ARM: > multi_v7_defconfig: enable drm imx support" is fine Agreed. It's perfect. > I think but in the commit message I missed the verb so this should be > a better one: > > --->8--- > ARM: multi_v7_defconfig: enable drm imx support > > Makes it possible to use multi v7 defconfig for stm32 and imx based devices with > full drm support. > --->8--- I don't think 'stm32' should be there, as the code change in this commit has nothing to do with stm32, if I understand it correctly. > How shall I proceed to get this change in? I can edit the commit log when applying. But we need to agree on what it should be first. Shawn