linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Thierry Reding <thierry.reding@gmail.com>,
	Rob Clark <robdclark@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Jagan Teki <jagan@amarulasolutions.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection"
Date: Thu, 21 Apr 2022 09:26:38 +0200	[thread overview]
Message-ID: <20220421072638.fw3prcfzdfheb7h3@houat> (raw)
In-Reply-To: <YmED/vYsrjoc4OjC@aptenodytes>

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

On Thu, Apr 21, 2022 at 09:13:02AM +0200, Paul Kocialkowski wrote:
> Hi,
> 
> On Wed 20 Apr 22, 16:19, Bjorn Andersson wrote:
> > On Wed 20 Apr 16:12 PDT 2022, Bjorn Andersson wrote:
> > 
> > Sorry, I missed Jagan and Linus, author and reviewer of the reverted
> > patch 2, among the recipients.
> 
> I'd be curious to have Jagan's feedback on why the change was needed in the
> first place and whether an accepted dt binding relies on it.
> 
> We might be able to just keep the whole thing reverted (forever).

I was the one that asked for it because I thought this would be more
convenient for everyone.

Turns out I was very wrong :)

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2022-04-21  7:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 23:12 [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection" Bjorn Andersson
2022-04-20 23:12 ` [PATCH 2/2] Revert "drm: of: Lookup if child node has panel or bridge" Bjorn Andersson
2022-04-21  7:20   ` (subset) " Maxime Ripard
2022-04-21  7:45   ` Jagan Teki
2022-04-21  8:23     ` Maxime Ripard
2022-04-21  8:59       ` Paul Kocialkowski
2022-04-26  7:54         ` Paul Kocialkowski
2022-04-26  8:10           ` Jagan Teki
2022-04-27 14:34             ` Maxime Ripard
2022-04-28  6:17               ` Marek Szyprowski
2022-04-28  8:25                 ` Jagan Teki
2022-04-28  8:39               ` Jagan Teki
2022-04-28 22:17                 ` Laurent Pinchart
2022-04-29  8:24                   ` Jagan Teki
2022-04-29 15:46                   ` Maxime Ripard
2022-04-29 16:05                     ` Laurent Pinchart
2022-05-04 15:08                       ` Maxime Ripard
2022-04-26 11:33           ` Laurent Pinchart
2022-04-26 12:41             ` Paul Kocialkowski
2022-04-26 12:54               ` Maxime Ripard
2022-04-26 12:55                 ` Maxime Ripard
2022-04-26 13:04                   ` Paul Kocialkowski
2022-04-26 13:19                     ` Maxime Ripard
2022-04-26 13:50                       ` Paul Kocialkowski
2022-04-26 21:10                         ` Bjorn Andersson
2022-04-27  7:34                           ` Paul Kocialkowski
2022-05-03  0:03                             ` Bjorn Andersson
2022-04-26 12:58                 ` Paul Kocialkowski
2022-04-27 13:10                 ` Laurent Pinchart
2022-04-26 12:51           ` Maxime Ripard
2022-04-27  6:59       ` Jagan Teki
2022-04-27 11:52         ` Jagan Teki
2022-04-27 12:19           ` Paul Kocialkowski
2022-04-27 12:59             ` Jagan Teki
2022-04-27 13:10           ` Laurent Pinchart
2022-04-20 23:19 ` [PATCH 1/2] Revert "drm: of: Properly try all possible cases for bridge/panel detection" Bjorn Andersson
2022-04-21  7:13   ` Paul Kocialkowski
2022-04-21  7:26     ` Maxime Ripard [this message]
2022-04-22  7:58     ` Raphael Gallais-Pou
2022-04-21  7:11 ` Paul Kocialkowski
2022-04-21  7:20 ` (subset) " Maxime Ripard

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=20220421072638.fw3prcfzdfheb7h3@houat \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=bjorn.andersson@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=robdclark@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=tzimmermann@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).