All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Olof Johansson <olof@lixom.net>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Patrice Chotard <patrice.chotard@st.com>,
	Joel Stanley <joel@jms.id.au>, Tony Lindgren <tony@atomide.com>,
	Lubomir Rintel <lkundrak@v3.sk>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	linux-arm-kernel@lists.infradead.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: enable drm imx support
Date: Wed, 19 Feb 2020 17:11:39 +0800	[thread overview]
Message-ID: <20200219091138.GA12803@dragon> (raw)
In-Reply-To: <CAH9NwWcNZzKt9gwYRRbgppeL9xqcK38z0ZP-5eGF9vXmg7T_=g@mail.gmail.com>

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 <shawnguo@kernel.org>:
> >
> > 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 <shawnguo@kernel.org>:
> > > >
> > > > 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
> > > > > <krzk@kernel.org>:
> > > > > >
> > > > > > On Mon, 10 Feb 2020 at 11:54, Christian Gmeiner
> > > > > > <christian.gmeiner@gmail.com> wrote:
> > > > > > >
> > > > > > > Am Fr., 24. Jan. 2020 um 09:44 Uhr schrieb Christian Gmeiner
> > > > > > > <christian.gmeiner@gmail.com>:
> > > > > > > >
> > > > > > > > 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

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Christian Gmeiner <christian.gmeiner@gmail.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	Lubomir Rintel <lkundrak@v3.sk>,
	Patrice Chotard <patrice.chotard@st.com>,
	Joel Stanley <joel@jms.id.au>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Olof Johansson <olof@lixom.net>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: multi_v7_defconfig: enable drm imx support
Date: Wed, 19 Feb 2020 17:11:39 +0800	[thread overview]
Message-ID: <20200219091138.GA12803@dragon> (raw)
In-Reply-To: <CAH9NwWcNZzKt9gwYRRbgppeL9xqcK38z0ZP-5eGF9vXmg7T_=g@mail.gmail.com>

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 <shawnguo@kernel.org>:
> >
> > 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 <shawnguo@kernel.org>:
> > > >
> > > > 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
> > > > > <krzk@kernel.org>:
> > > > > >
> > > > > > On Mon, 10 Feb 2020 at 11:54, Christian Gmeiner
> > > > > > <christian.gmeiner@gmail.com> wrote:
> > > > > > >
> > > > > > > Am Fr., 24. Jan. 2020 um 09:44 Uhr schrieb Christian Gmeiner
> > > > > > > <christian.gmeiner@gmail.com>:
> > > > > > > >
> > > > > > > > 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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-02-19  9:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24  8:43 [PATCH] ARM: multi_v7_defconfig: enable drm imx support Christian Gmeiner
2020-01-24  8:43 ` Christian Gmeiner
2020-02-10 10:54 ` Christian Gmeiner
2020-02-10 10:54   ` Christian Gmeiner
2020-02-10 10:58   ` Krzysztof Kozlowski
2020-02-10 10:58     ` Krzysztof Kozlowski
2020-02-10 13:30     ` Christian Gmeiner
2020-02-10 13:30       ` Christian Gmeiner
2020-02-17  4:19       ` Shawn Guo
2020-02-17  4:19         ` Shawn Guo
2020-02-17 12:09         ` Christian Gmeiner
2020-02-17 12:09           ` Christian Gmeiner
2020-02-18  9:14           ` Shawn Guo
2020-02-18  9:14             ` Shawn Guo
2020-02-19  8:48             ` Christian Gmeiner
2020-02-19  8:48               ` Christian Gmeiner
2020-02-19  9:11               ` Shawn Guo [this message]
2020-02-19  9:11                 ` Shawn Guo
2020-03-06 13:58                 ` Christian Gmeiner
2020-03-06 13:58                   ` Christian Gmeiner
2020-03-10  3:29                   ` Shawn Guo
2020-03-10  3:29                     ` Shawn Guo
2020-02-14  7:22 Christian Gmeiner
2020-02-14  7:22 ` Christian Gmeiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200219091138.GA12803@dragon \
    --to=shawnguo@kernel.org \
    --cc=alexandre.torgue@st.com \
    --cc=arnd@arndb.de \
    --cc=christian.gmeiner@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=joel@jms.id.au \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkundrak@v3.sk \
    --cc=olof@lixom.net \
    --cc=p.zabel@pengutronix.de \
    --cc=patrice.chotard@st.com \
    --cc=s.hauer@pengutronix.de \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.