All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: hs@denx.de, linux-arm-kernel@lists.infradead.org,
	sboyd@kernel.org, abelvesa@kernel.org, linux-clk@vger.kernel.org,
	Fabio Estevam <festevam@denx.de>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 1/3] ARM: dts: imx6sx: Remove LDB endpoint
Date: Sun, 30 Jul 2023 11:12:55 +0800	[thread overview]
Message-ID: <20230730031255.GU151430@dragon> (raw)
In-Reply-To: <20230712115301.690714-1-festevam@gmail.com>

On Wed, Jul 12, 2023 at 08:52:59AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
> 
> Remove the LDB endpoint description from the common imx6sx.dtsi
> as it causes regression for boards that has the LCDIF connected
> directly to a parallel display.
> 
> Let the LDB endpoint be described in the board devicetree file
> instead.
> 
> Cc: stable@vger.kernel.org
> Fixes: b74edf626c4f ("ARM: dts: imx6sx: Add LDB support")
> Signed-off-by: Fabio Estevam <festevam@denx.de>

Applied, thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: hs@denx.de, linux-arm-kernel@lists.infradead.org,
	sboyd@kernel.org, abelvesa@kernel.org, linux-clk@vger.kernel.org,
	Fabio Estevam <festevam@denx.de>,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 1/3] ARM: dts: imx6sx: Remove LDB endpoint
Date: Sun, 30 Jul 2023 11:12:55 +0800	[thread overview]
Message-ID: <20230730031255.GU151430@dragon> (raw)
In-Reply-To: <20230712115301.690714-1-festevam@gmail.com>

On Wed, Jul 12, 2023 at 08:52:59AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <festevam@denx.de>
> 
> Remove the LDB endpoint description from the common imx6sx.dtsi
> as it causes regression for boards that has the LCDIF connected
> directly to a parallel display.
> 
> Let the LDB endpoint be described in the board devicetree file
> instead.
> 
> Cc: stable@vger.kernel.org
> Fixes: b74edf626c4f ("ARM: dts: imx6sx: Add LDB support")
> Signed-off-by: Fabio Estevam <festevam@denx.de>

Applied, thanks!

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

  parent reply	other threads:[~2023-07-30  3:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 11:52 [PATCH v3 1/3] ARM: dts: imx6sx: Remove LDB endpoint Fabio Estevam
2023-07-12 11:52 ` Fabio Estevam
2023-07-12 11:53 ` [PATCH v3 2/3] ARM: dts: imx6sx: Describe the default LCDIF1 parent Fabio Estevam
2023-07-12 11:53   ` Fabio Estevam
2023-07-30  3:13   ` Shawn Guo
2023-07-30  3:13     ` Shawn Guo
2023-07-12 11:53 ` [PATCH v3 3/3] clk: imx: imx6sx: Remove hardcoded " Fabio Estevam
2023-07-12 11:53   ` Fabio Estevam
2023-08-15 12:34   ` Fabio Estevam
2023-08-15 12:34     ` Fabio Estevam
2023-08-15 12:49     ` Fabio Estevam
2023-08-15 12:49       ` Fabio Estevam
2023-07-23 23:41 ` [PATCH v3 1/3] ARM: dts: imx6sx: Remove LDB endpoint Fabio Estevam
2023-07-30  3:12 ` Shawn Guo [this message]
2023-07-30  3:12   ` Shawn Guo

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=20230730031255.GU151430@dragon \
    --to=shawnguo@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=festevam@denx.de \
    --cc=festevam@gmail.com \
    --cc=hs@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=stable@vger.kernel.org \
    /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.