dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Heiko Stuebner <heiko@sntech.de>,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH 0/3] drm/panel: Proper cleanup after mipi_dsi_attach()
Date: Thu, 14 Oct 2021 21:59:47 +0200	[thread overview]
Message-ID: <YWiMMzvKHxQJcVoh@ravnborg.org> (raw)
In-Reply-To: <20210924003355.2071543-1-briannorris@chromium.org>

Hi Brian,

On Thu, Sep 23, 2021 at 05:33:52PM -0700, Brian Norris wrote:
> I've tested a few dual-DSI panel drivers which choke if they PROBE_DEFER
> at the wrong time, so I patched those up in patch 1 and 2. Patch 3 fixes
> the other drivers that I couldn't test, but seem to have all the same
> problem.
> 
> 
> Brian Norris (3):
>   drm/panel: kingdisplay-kd097d04: Delete panel on attach() failure
>   drm/panel: innolux-p079zca: Delete panel on attach() failure
>   drm/panel: Delete panel on mipi_dsi_attach() failure

Thanks for fixing these up, and especially for the fix of the remaining
panel drivers.

I have applied all three patches to drm-misc-next as I did not consider
the fixes urgent.

They will show up in -next in 1-2 weeks.

	Sam

      parent reply	other threads:[~2021-10-14 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24  0:33 [PATCH 0/3] drm/panel: Proper cleanup after mipi_dsi_attach() Brian Norris
2021-09-24  0:33 ` [PATCH 1/3] drm/panel: kingdisplay-kd097d04: Delete panel on attach() failure Brian Norris
2021-09-24  0:33 ` [PATCH 2/3] drm/panel: innolux-p079zca: " Brian Norris
2021-09-24  0:33 ` [PATCH 3/3] drm/panel: Delete panel on mipi_dsi_attach() failure Brian Norris
2021-10-14 19:59 ` Sam Ravnborg [this message]

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=YWiMMzvKHxQJcVoh@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=briannorris@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=thierry.reding@gmail.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 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).